Replying to @⁨nikitonsky@mastodon.online⁩

@nikitonsky

I really like this as an install flow, because it's all about direct manipulation. The application is a thing that you can pick up and use. The applications folder may be a simple flat space, but if you put the Finder in spatial mode then you can arrange things however you like and rely on spatial memory.

Windows 3.x's Program Manager looked like the Finder, but it was an extra indirection layer. From Windows 95, Microsoft completely visually separated the thing that is the program in the filesystem from the thing that you click to launch the program and never regained that connection.

But the place it falls down is uninstallation. Modern apps are stateful. At a minimum, they will record window positions in User Defaults on macOS, but they may also safe other preferences there. They may have local caches of data. They may have documents that you'd want to keep (for example, images that another program can open) or ones that are explicitly linked to the program (such as savegames). When you uninstall a program on macOS, you drag it to the bin, but that just removes the program, not any of that other stuff.

I vaguely recall a BeOS derivative providing a hook for when things are moved out of folders that you could use to clean things up.

en

Replying to @⁨drq@mastodon.ml⁩

@drq I think there's two kind of apps, or even use-cases

Type 1 is a tool. You get it to do the task, you do the task, you put tool away so it doesn't bother you

Type 2 is a module. You get it, put it in your system, do some wiring and pairing, configure it to your needs. Make some choices. In return, a module will empower you in day-to-day activities, for a long time

neither of those types is superior to other, they are just for different users, and solve different needs

@david_chisnall @nikitonsky