Linked by Kroc Camen on Thu 5th Nov 2009 21:05 UTC
Talk, Rumors, X Versus Y There's no right way to do it, only ideas that are better than others in certain situations. But if you had the opportunity to head up the design of a new OS, one to Put Things Right, one that could be radical enough to varnish out those UI/X bumps that have clung on for years, but practical enough to be used every day, what would you design? How would you handle application management? What about file types and compatibility? Where would you cherry pick the best bits from other OSes and where would you throw away tradition? I've tackled this challenge for myself and present (an unfinished idea): KrocOS (warning: HTML5 site, will display without CSS in IE/older browsers). OSnews Asks: What would make your perfect OS?
Thread beginning with comment 393191
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Why was he modded down?
by Slambert666 on Fri 6th Nov 2009 08:34 UTC in reply to "RE: Why was he modded down? "
Slambert666
Member since:
2008-10-30

However, a stable ABI for drivers would be extremely bad. I love open source, but I understand that there are valid reasons to create closed source/commercial software. However, there is no reason at all why a driver should be closed source. It simply doesn't make sense. Closed source drivers are less secure, hold back progress in the kernel, and make reduce portability. The only reason for closed source drivers that is even at all close to being somewhat valid is to protect IP. But that really only applies to graphics cards. And even then, I imagine it's just nVidia being lazy.


A stable abi is not the same as closed source (!)

Drivers are one of the most nasty, buggy and system dependent pieces of code that one can write. There are so many testing what if's and maybe's involved that it is horrible. Every time you change the interface of a driver (class) you need to test not just that driver but also the drivers interaction with all possible combination's of other drivers / hardware.

The Linux kernel developers are delusional of their own capabilities to such an extent that they think they can change driver interfaces and release the code without testing. In a given iteration 90% or more of the code never gets tested and the small part that actually gets tested doesn't work, this is labeled "regressions" and each release has a number of these.
A stable abi would be the first step on the way to a more systematic testing framework for the kernel and related drivers.

Reply Parent Score: 1