3 ms·
> Is this a real hard problem to solve? Somewhat. On the one hand, you have plain old feature creep – people expect smoother animations, more animations, more
by creshal 11y ago
> Is this a real hard problem to solve?
Somewhat. On the one hand, you have plain old feature creep – people expect smoother animations, more animations, more features, better fleshed out features, … and it's hard to resist those demands when you want to sell your software.
One the other hand, you have security and reliability. All those error checks, bounds checks, canary checks, validations, secure hand shakes, … take up time, and it accumulates. DOS was fast, but it was also terribly insecure and most programs crashed regularly.
- uptownhr 11y agoDOS, wasn't really multitasking OS anyways. I think my main point is, is it hard to preserve and give OS high priority over all other applications? If it is not hard, is a big downside for app developers if they don't get 100% control over the CPU cycles? Why is it necessary these days that apps have the ability to push 100% on multiple cores? At the least with multiple cores, shouldn't 1 core be dedicated to the OS, so it never hangs due to another app? Something sacred, with a lot of gates so devs cannot mess up the entire OS and user experience due to their app.