Slashdot Mirror
Linux Turns 25, Is Bigger and More Professional Than Ever (arstechnica.com)
The Linux operating system kernel is 25 years old this month, ArsTechnica writes. It was August 25, 1991 when Linus Torvalds posted his famous message announcing the project, claiming that Linux was "just a hobby, won't be big and professional like gnu." From the article: But now, Linux is far bigger and more professional than Torvalds could have imagined. Linux powers huge portions of the Internet's infrastructure, corporate data centers, websites, stock exchanges, the world's most widely used smartphone operating system, and nearly all of the world's fastest supercomputers. The successes easily outweigh Linux's failure to unseat Microsoft and Apple on PCs, but Linux has still managed to get on tens of millions of desktops and laptops and Linux software even runs on Windows.Do you use any Linux-based operating system? Share your experience with it. What changes would you want to see in it in the next five years?
What changes would you want to see in it in the next five years?
Still waiting for the year of the desktop. A viable alternative to osx (and ms) for multimedia work, specifically, professional level audio engineering work.
If I may, and even if I mayn't, I'm going to rant about the same thing I always rant about in these stories: usability. Desktop Linux is a great operating system for those who have put in the many hours needed to understand its quirks. It's a great operating system for people who never so much as install a new sound driver. For the remaining 80% of users it's a usability nightmare. The wide range of distro's running the Gnome and KDE mean many common interactions differ between computers. And the Linux/Unix ideology of each program doing one thing (and doing it well) means which programs a user will have is unpredictable.
This, in turn, means it's all but impossible to provide a simple, straightforward instruction to a user for how to do something with her machine. Even something that should be dead simple. As soon as a user has to modify a config file or open a command prompt that's a huge roadblock. And no I'm not saying "be like Windows". That implication is a cop-out.It's not about doing things the way Windows does them, it's about making it "just work", and when it doesn't offering highly intuitive graphical interfaces for changing the way it works.
The Linux development community has made huge strides in this direction, but more is needed. Write drivers that interface with Gnome and KDE environments and provide GUI's for every setting. If a driver doesn't gave a Gnome and KDE GUI that covers 99.99% of use cases it's not finished. Make it so a user never, ever has to open a command prompt. Stick to the top three or fewer interfaces, and make them rock solid. No more installing interfaces to install interfaces to install decompressers to compile drivers. Do this and you shall see the year of Linux on the desktop.
If video games influenced behavior the Pac Man generation would be eating pills and running away from their problems.
Agreed. It is pretty phenomenal that Linux runs on over 2 billion device. You're absolutely right on scalability: from cell phones all the way up to 99.4% of supercomputers. WOW.
Hopefully nVidia and AMD will continue to support OpenGL on the desktop so that Linux can continue to make inroads into high performance heterogeneous computing & gaming.
What's ironic is for MS to have once called "Linux is a cancer" to now admitting that they use it on 33% of their Azure servers!
* http://news.microsoft.com/byth...
* http://fossbytes.com/33-micros...
Not bad for the little OS that could. :-)
You are confusing contributing with leading the project.
Determining what code is written, what new features are developed, is leading the project. Not merging the contributions after ensuring the code is well written.
Linus leads from behind. After a feature is developed, he decides whether it will be allowed into the kernel. It's the same sort of decisionmaking process as in most development workflows, it just front-ends most of the work.
In most development processes, someone will decide "the product should do X", and they'll make some slides and pitch the ideas and the leaders will decide whether or not to pursue it. If they decide to pursue it then the developers will build it, debug it, test it, etc. The process is optimized around conserving a scarce resource, developer time.
In the Linux process, someone decides "Linux should do X", and so they build it, write all the code, debug it, test it... and then they'll send it to Linus, who decides whether or not to merge it. Same process, the difference is that the leader decides on the basis of fully-implemented code, rather than slideware. In the Linux model, developer time is not scarce and the process does not optimize for conserving it.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.