|
|
|
|
|
by tytso
331 days ago
|
|
This is ultimately a business model problem. There are FOSS projects out there; some of them are even listed in the article. The problem is that making it "Just Work(tm)" is hard; it's a lot of work, requiring a large number of engineers. And funny thing, engineers prefer food with their meals. Saying "FOSS world" we need XXX is pretty useless. As a FOSS mainatinaer, the answer I always give people demanding their favorite pet feature is, "clean, maintainable patches are appreciated", ChromiumOS is free software; someone could take it use it as the basis for something like ChromeOS. But the author of the article has basically admitted that the derivitives of Chromium would quickly fail if Chromium stoped being something that they could free ride off of. Shouldn't that tell you everything about what the problem is with this picture? |
|
Programmers often stop worrying about the details once they're satisfied, though, and there are a lot of details. Yes we could add thumbnails to the file picker, but we also need to support Nvidia hardware and the archive application is missing a few much more interesting compression formats, plus there are a bazillion logged bugs that actually crash software rather than being a minor inconvenience.
In theory someone could set up a collective of programmers, designers, and translators to create a usable Linux desktop for the Windows 10 refugees, but it'll require a lot of effort from a lot of volunteers and a lot of people who happen to share the same principles and preferences.
ChromeOS works because there's a single entity that can hire a small group of designers to tell an army of programmers what they want everything to look and work like.
There are actually projects and companies that fork ChromeOS, but they're pretty small and once Google stops maintaining the OS they're going to collapse pretty quickly.