> Considering the huge progress that was made in the 90'ties on Linux and the lack of progress done after OS X came, I think it is safe to assume that OS X played a major role here.
Progress in software development is not linear. You quickly get the basics done, and then the devil in the details. Also, the Gnome vs. KDE feud didn't help one bit.
That said, OS X being exactly what Linux dreams to be (Unix with a beautiful and useable UI, scriptable apps, reusable components, and a modern development platform), I know I'm not the only one to whom it provided a haven after years of Linux-induced frustration.
> Desktop Linux seems to me that it was created by stitching obsolete software and quick hacks together with glue and spit. Even broken as it is, I still marvel at how functional it is for me. And even unpopular as it is, there are some normal people using it, which goes to show that it isn't totally broken or insane.
No disagreement here.
> I don't agree there - having the source is a huge advantage, even if you aren't capable of modifying it. Just as with cars, you don't necessarily have to go to the parent company and you don't have to fix it yourself. You can always choose a local shop for repairing and tunning.
In theory it's true, in practice it rarely is, since taking over a code base of any significant size is a very hard challenge. I've yet to encounter a situation like you describe, or even hear about one. When the software doesn't work, you replace it, source available or not.
> I wonder why are you saying that, when server-side Linux and related software is such a huge hit.
Because the audience being other tech geeks, it's a much simpler endeavor.
> You can also point out to some desktop software that is free software, that is sponsored and yet community driven and that is usable.
Sponsored free software is usually mostly developed by the company sponsoring it, the community comes a distant second. This is a scheme which works, though, as the company has the final say. I hope it will keep on growing.
In theory it's true, in practice it rarely is, since taking over a code base of any significant size is a very hard challenge. I've yet to encounter a situation like you describe, or even hear about one. When the software doesn't work, you replace it, source available or not.
Even if you're replacing the software, having the source allows you to ensure that your replacement is fully backwards compatible with the original, and, if it is not, enables you to implement a compatibility shim that fixes those issues.
That said, OS X being exactly what Linux dreams to be (Unix with a beautiful and useable UI, scriptable apps, reusable components, and a modern development platform), I know I'm not the only one to whom it provided a haven after years of Linux-induced frustration.
You can't just blame the Linux community, though. I agree that the community could do a lot of things better (especially with regards to UI development). However, one big obstacle the Linux community has to work against is hardware support. Windows is the dominant OS - manufacturers essentially subsidize Microsoft by providing Windows drivers for their product. Apple, by choice, writes OSX to only work on a very limited subset of devices that have been approved by Apple. Linux has neither of those advantages.
In theory, the fact that Linux is open should make it easier for programmers to make their own drivers and release those drivers to the community at large. In practice, because of many of the concerns that you've cited, proprietary drivers still outclass Linux drivers for a number of components, including WiFi, ACPI power management, and graphics.
Even if you're replacing the software, having the source allows you to ensure that your replacement is fully backwards compatible with the original
Same answer : True in theory, very rarely practical in reality. The only thing that really matters is the spec of the data format used by the program.
You can't just blame the Linux community, though.
I agree, it's not just that, but it's the main reason. 15 years since the start of KDE and there's still no sign of a unified, viable platform. If there was one, hardware support would follow.
Progress in software development is not linear. You quickly get the basics done, and then the devil in the details. Also, the Gnome vs. KDE feud didn't help one bit.
That said, OS X being exactly what Linux dreams to be (Unix with a beautiful and useable UI, scriptable apps, reusable components, and a modern development platform), I know I'm not the only one to whom it provided a haven after years of Linux-induced frustration.
> Desktop Linux seems to me that it was created by stitching obsolete software and quick hacks together with glue and spit. Even broken as it is, I still marvel at how functional it is for me. And even unpopular as it is, there are some normal people using it, which goes to show that it isn't totally broken or insane.
No disagreement here.
> I don't agree there - having the source is a huge advantage, even if you aren't capable of modifying it. Just as with cars, you don't necessarily have to go to the parent company and you don't have to fix it yourself. You can always choose a local shop for repairing and tunning.
In theory it's true, in practice it rarely is, since taking over a code base of any significant size is a very hard challenge. I've yet to encounter a situation like you describe, or even hear about one. When the software doesn't work, you replace it, source available or not.
> I wonder why are you saying that, when server-side Linux and related software is such a huge hit.
Because the audience being other tech geeks, it's a much simpler endeavor.
> You can also point out to some desktop software that is free software, that is sponsored and yet community driven and that is usable.
Sponsored free software is usually mostly developed by the company sponsoring it, the community comes a distant second. This is a scheme which works, though, as the company has the final say. I hope it will keep on growing.