What Killed the Linux Desktop (2012)
For anyone who skipped the comment section of the article, I found the following comment by &quot;has&quot; to be very insightful. Specifically the way that the community would rather divide its resources to keep multiple mediocre implementations of a given thing around than consolidate them, and how the Unix Philosophy has been ignored:<p>@Miguel: You are right about developer culture being a huge factor. Linux geeks all to often see the OS as the end in itself, whereas the rest of the world knows the OS is merely the means to an end. The OS is the least important component in the ecosystem: what actually matters is the applications and services they can use to get things done. Either it enables that or it obstructs it.<p>You also mentioned excessive fragmentation as being one of those obstructions. Now, I do believe the &#x27;let a thousand flowers bloom&#x27; approach of the OSS world is valuable: where it completely falls down is in its abject failure to asset-strip the less successful variants for whatever merits they have unveiled, then put them wholesale to the sword. Evolution doesn&#x27;t succeed by ideology or sentimentality; it works through merciless competition culling the weak so the strongest may dominate.<p>The best immediate remedy for Linux&#x27;s desktop ills would be to put 80% of current DEs to the axe. Really you only need three mainstream distros: one to cover general users (Ubuntu; sorry Gnome 3), one to cover the inveterate tinkerers (KDE), and one to cover the reactionary conservatives (one of the Gnome 2 clones&#x2F;derivatives). Retain a few specialised distros for niches such as very elderly&#x2F;low-powered machines (hi, Pi!) and security work. Anything else is a research project to produce new ideas that can then be stolen by the mainstream distros, or just a leach on the body Linux that should be salted forthwith that the rest may grow stronger.<p>...<p>However, I think you completely missed one other valuable - and uncomfortable - point; arguably the most essential of them all.<p>While addressing the excessive dilution of manpower and message may help in the short term, there is a far more fundamental cultural problem: the Linux desktop world (and even the kernel world beneath it) has <i>completely and utterly forgotten its roots</i>. Unix Philosophy isn&#x27;t merely a neat marketing phrase: it describes a <i>very</i> specific way to construct large, complex systems. Not by erecting vast imposing monoliths, ego-gratifying as that may be, but by assembling a rich ecosystem of small, simple, plug-n-play components that can be linked together in whatever arrangement best suits a given problem.<p>By mimicking the Apple and Microsoft tactic of constructing vast monolithic environments and applications, you have all unwittingly been playing to <i>their</i> strengths, not yours. Such enormous proprietary companies can afford such brute-force strategies because they have vast financial and manpower resources to draw on. Indeed, it works in their favour to do so because vast monolithic applications help to create user lock-in: look at Adobe Creative Suite; look at Microsoft Office. Nobody can truly compete with them because to assemble comparably featured applications takes at least a decade: until then, any competing applications are fewer featured and far more susceptible to being excluded by the vast user-side network effect that the big boys have formed around themselves.<p>Conversely, look at what has happened when the above vendors have tried to take a more component-oriented approach. For instance, Apple&#x27;s attempt to implement OpenDoc failed not because it was fundamentally, fatally flawed at the technical level. (It may not have been perfect, but what is? It was still a good and promising platform in itself.) It failed because the business model it proposed - lots of small, cheap, single-purpose components from many vendors that users could purchase and mix-and-match however they liked - was utterly disruptive and utterly incompatible to the business model used by the very application vendors that Mac OS relied on to survive. Adobe&#x27;s control of the market was predicated on it being the 800-pound gorilla in the room; it was <i>never</i> going to give that up by choice.<p>Whereas the Linux business model has no such requirements for maintaining artificial scarcity; indeed, given its far more limited development resources, it should be pouring every ounce of its strength into finding ways to work smart, not hard, like this. Unix Philosophy was a reaction to the inescapable hardware limitations of the day; now those limitations are no longer enforced, <i>nix developers have gotten flabby and soft. They build these vast, inflexible edifices simply because they are not required to find a more ingeniously efficient way, and because as a short-term strategy diving straight in and copying how everyone else already does it is inevitably the easiest, laziest approach available. As a long-term strategy, however, it&#x27;s an absolute disaster. Projects like Gnome and Open Office become like our banking industries: vast, baroque, impossible to regulate effectively, and cripplingly expensive to maintain.<p>The result is: vast projects that are </i>far too big to fail<i>. The thought of axing, say, Gnome 3 - not on technical merit but simply because it consumes too much resource from Linux as a whole - becomes unthinkable. So rather than killing it and folding its best bits into other, fewer distros, even more manpower must be poured into keeping it going and looking like it actually serves a critical purpose instead of acting as yet another boat anchor on the whole show. Manpower that should&#x27;ve been invested in finding ingenious ways to play to Linux&#x2F;Unix&#x27;s unique strengths, not to its competition&#x27;s.<p>Apple didn&#x27;t go from virtually dead husk to #1 in the whole damned industry by continuing to play Microsoft&#x27;s game by Microsoft&#x27;s rules. It did it by looking at what MS and all its other competitors </i>weren&#x27;t* doing, or weren&#x27;t doing well, in order to meet consumers wants and needs, then devising a cunning plan to do a complete end-run around the lot of them: redefining the entire game to suit their own strengths and allow them to define their own rules. Even if it meant burning their own traditional platform to get there. It was an absolute masterstroke, and a prime reminder that if you want to understand how this game is really played, you don&#x27;t read Slashdot, you read Sun Tzu.<p>...<p>TL;DR: Windows didn&#x27;t kill the Linux desktop and neither did OS X. The Linux desktop killed itself, by playing on their terms instead of its own. The best thing it can do now - once denial and recrimination are done with - is turn the killing process itself into a virtue, and slice not only the DE&#x2F;application mess but also the cultural one right back down to the bone and start rebuilding from there.<p>Good luck, and apologies for length.