6 ms·
you still haven't defined the "fragmentation" You're unfamiliar with Linux distros? There more than twenty "desktop Linux" distros mentioned here: http://www.
by randallsquared 16y ago
you still haven't defined the "fragmentation"
You're unfamiliar with Linux distros? There more than twenty "desktop Linux" distros mentioned here: http://www.desktoplinux.com/articles/AT7386380154.html http://www.desktoplinux.com/articles/AT7386380154.html , and that's merely the "especially interesting" ones. In contrast, there are probably less than 20% of OS X users on versions of OS X older than 10.4, and binary compatibility isn't a major issue for anyone except Windows.
OS X, which breaks backwards compatibility more often than Linux (like once every 2 or 3 versions).
That's true, but while there are tools to mitigate that (Rosetta, Classic), it's completely orthogonal to what I'm talking about, as is your server-side software.
Your point about software that "can be made to work" is exactly spot on: virtually anything is possible, in a way that it's not always possible on Mac or Windows, but almost nothing is easy.
I have never seen an install of desktop Linux where the install went smoothly and it found all the hardware and correctly set it up, and all the settings did what they say they do, and all the software available in the built-in software installation tool actually worked. As soon as a person unfamiliar with what to avoid starts playing around with a desktop Linux install, things start to go wrong, and if they're lucky it's a dozen little things that just don't quite work right, and if they're unlucky they stumble into things that really make the system unusable.
I've seen this happen over and over with friends I'd encouraged to try Linux when they were griping about Windows, and I know of only one group (a family) who successfully made the switch. How did they do it? Well, they've learned not to try to adjust things too much, and they mostly keep their hands inside the cart and sit very still, and when things go wrong they quietly wait for the next Ubuntu release in the hopes that the problem will be fixed without too much other stuff breaking. Oh, and they purchased Ubuntu-specific hardware, but things still stop working randomly on update from time to time.
This is what I mean by having a QA problem. Desktop Linux needs a thousand QA and dev people focused on tracking down and fixing all these issues, and it can't get them, and I don't see any way that's going to change.
Edit: Oh, and you'd have to fork about a thousand different pieces of software to achieve consistency and interoperability that didn't immediately fall apart on the next minor release of those applications. Putting together a coherent Linux desktop seems like one of those things where we should be surpised that anyone succeeds at all, rather than upset that they didn't do well at it. "It's not how well the bear dances", and all that.
- bad_user 16y agoWell, yeah, you've got some good points there. All I'm saying is that fragmentation never bothered me so much, and even on Linux where you've got a thousand options available, there are a couple of paths that you can go on which will make everything less painful. When it comes to Android development, yes you need to test on multiple devices, but what's mostly broken is the design that has to have adjustments for multiple resolutions ... but then again, I haven't done stuff too complicated thus far. I feel this is the same gripe people have with the web, where I do have experience and where fragmentation never was an issue for me. All I had to do was to look around for abstractions, and for IE hacks try not to reinvent the wheel on every single project (and just ignore IE6 since about a year ago, but with a nice warning for users to know what's going on).