Please try doing some GUI programming, your ideas sound good in the abstract, but they fail when you get down to trying to use them
Taking your mouse example, some graphics cards do support hardware mouse cursors, where the card handles moving the mouse pointer.
however, such support really doesn't help much and is fading from use today because nowdays people want to change the shape of the cursor depending on what you are doing, etc.
you also have to think about how the program should know that it should look for an update to the mouse position. you don't want it spinning in a loop when nothing happens.
you also don't just want the current position of the mouse, you want to know it's path, and how fast it's moving (along with what buttons, if any are pressed during any part of this time)
There are pretty good reasons that systems do things the way they do. People have tried a LOT of things over the years, and what's in place may not be the perfect way to do things, but they've survived lots of competing ideas along the way.
Posted Dec 19, 2012 23:03 UTC (Wed) by man_ls (subscriber, #15091)
[Link]
I know this is just another load of armchair OS design, and that it will not probably work in real life, but perhaps it is worth a try for somebody.
Remember that this article refers to node.js. People have tried many things over the years in the web server arena, and around 2000 Apache was the clear market leader, with Microsoft a distant second. Apparently everything had been invented already. Then in 2002 a Russian guy decided to start development on a different model. Guess what: 10 years later it is the second web server in actives, ahead of Microsoft IIS. A year ago some crazy guys took Google's V8 engine and coded a web server around it, not in C or C++ but in... JavaScript. Preposterous. The result: the new web server everyone is talking about, capable of sustaining thousands of requests per second out of the box.