Linked by Thom Holwerda on Mon 5th May 2008 21:00 UTC
OSNews, Generic OSes Ever since I started using computers, I've been baffled by the relative clumsiness of installing applications. Whether we are talking the really old days (launching the Rambo game off a tape), the '90s (running Keen or using installers in Windows 95), or the modern days (still those installers, but now also package management and self-contained applications); it's all relatively cumbersome, and they all have their downsides. I decided to put my money where my mouth is, and come up with my idealistic, utopian method of installing, running, updating, and uninstalling applications.
Permalink for comment 313054
To read all comments associated with this story, please click here.
RE: some ideas for refining
by Thom_Holwerda on Tue 6th May 2008 10:24 UTC in reply to "some ideas for refining"
Thom_Holwerda
Member since:
2005-06-29

is this meant for Windows, OS X (OS XI?), Linux, some other OS, or an entirely new system?


It's not meant for any specific system, but you can see my involvement in Haiku and my love for BeOS shining through.

Supporting multiple versions of a program in parallel, sharing the same set of settings


Except, they don't. The whole idea is that the the directory /Settings/User 1/Garden Designer could contain multiple settings files for multiple versions - just as I explained in the article. They would be differentiated by their internal version numbers. The file manager could show them as follows:

/Settings/User 1/Garden Designer/settings.xml:438
/Settings/User 1/Garden Designer/settings.xml:439

The same goes for the programs:

/Programs/Garden Designer.bundle:438
/Programs/Garden Designer.bundle:439

The idea is that the system is clever enough to only display the internal version number when there are actually multiple versions installed. Since installing multiple versions is most likely an expert endeavour only, normal users will never encounter such internal version numbers attached to their program bundle files.

Finally, the proposed system also does not seem to support installing programs without system privileges, which is normally possible for most Linux / OSX software and an increasing share of Windows software.


Installing Linux packages without system privileges? Some exotic Zero Install systems may be, but other, more conventional package systems all require system access (as far as I know).

Anyway, executable code should never be able to be installed without a system password, if you ask me. I'm quite strict in that, I know. Executable code is the basis for A LOT of attacks, so it simply shouldn't be something just any user can dump on the system.

Edited 2008-05-06 10:31 UTC

Reply Parent Score: 1