To view parent comment, click here.
To read all comments associated with this story, please click here.
Confusing.
Select one of the myriads installers for Windows - it will work for Windows.
Select one of myriads repos (or w/e) for Linux - it will work for Linux (Debian) but not for Linux (Fedora, SuSE, Arch, Gentoo, etc).
And Linux also becomes a mess - leftover log, configuration files. Same as Windows. Doesn't work any slower, you just lose some kilobytes of space from your storage which has more than terabyte.
Central update - well duh. That isn't how Windows software works. I just cannot fathom how quality software could be upgraded via free of charge to newest version. When Ubuntu will be able to upgrade my Photoshop, Visual Studio, Sony Vegas or w/e via apt-get upgrade, then this "central" thingy argument might work. Right now - woo new updates for some random libraries that a non factor programs uses and I don't get any new features/performance. Woo exciting indeed.
How Windows is a mess again?
Edited 2012-12-25 11:57 UTC
Except none of those even run on Linux in the first place so why would the upgrade work? Logic, you fail it.
That's like complaining that Windows can't update my Linux e17 installation.




Member since:
2005-07-06
> If you are telling me that it's not possible to install a framework and a set of apps with an installer then you must be relatively new to computers.
Of course, it's "possible", but on Linux platforms it's highly "undesirable". This is because, unlike Windows, it actually has a common installer (rpm or dpkg) and repo system (yum or apt-get) already, so to be frank, anyone writing their own installer for Linux binaries should be taken out around the back and whipped to within an inch of their lives :-)
What devs need to do - and they often epicly fail at this - is to actually make it easier for the distro maintainers to build an RPM/.deb/whatever out of their source code. This means making sure that everything installs into the appropriate trees, including necessary package config files (e.g. .spec files for RPM) and so on.
Having said all this, it does highlight one of the majorly broken issues of package installation on Linux - there needs to be *one* binary package format and *one* repo format before this mess ever gets properly cleared up.
It would also be nice if everyone agreed the same install trees too - if all of the above happened, we might see the day where everything in Debian, Ubuntu, Fedora, CentoS/RHEL and openSuSE is completely interoperable/installable. Sadly, the chaos we're in doesn't look like sorting itself out any time soon.
It should be noted that Windows is actually worse mess - no central repo across all apps (Windows Update is MS products only, which is ludicrous) and there are literally hundreds of different installers written out there which have wildly variable behaviour.
Custom binary installers are *not* the way to go and yet Windows people seem to happy to use them. The problem with those installers is there's often no easy way to tell what or where they've installed or if they've left anything behind on uninstallation (which they often do). It's exactly why Windows PCs get into a mess as they go through installations and uninstallations of third-party software.