Linked by Kroc Camen on Thu 5th Nov 2009 21:05 UTC
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 393531
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-02
*yawn* Linux is FOSS. Non-free binary drivers have proven to be problems for the maintainers of FOSS kernel bits in the past. Linux devs and maintainers do not want binary (black-box) drivers. A stable ABI only benefits makers of binary (binary) drivers.
Currently, plain old buggy drivers are a problem (Do Atheros G cards work with this kernel version? Try it and see!), but the kernel's internal functions changing faster than the maintainers can keep up has helped cause issues, before. A stable API (for certain definitions of A) would reduce the work needed by maintainers of various drivers, at what should be a very minor cost (provided the API is planned out, not just frozen as it is now) to the people working on related parts of the kernel, and likewise, a very minor cost in terms of memory complexity of the kernel.