3 ms·
Didn't BeOS get this right? I too wonder why UI threads are still so obnoxiously tied to... everything else. Put UI in the fast lane! (At least until some bug
by tomc1985 8y ago
Didn't BeOS get this right?
I too wonder why UI threads are still so obnoxiously tied to... everything else. Put UI in the fast lane! (At least until some bug tries to make a bajillion calls a second)
Then I remembered how much more complicated it is to write proper multithreaded GUI code :P
- rangibaby 8y agoI remember Safari in the iPhone 3G would ALWAYS scroll even if it meant showing a checkerboard pattern while the page rendering caught up.
- tomc1985 8y agoSafari did that for a while too
- speedplane 8y agoI remember old Mac OS 9. If you started a print job, and held down the mouse holding down a click, the printer would just stop. The entire system wasn't properly multi-threaded.
- dasmoth 8y agoThat’s something that I remember people in my circle joking about at the time, but in retrospect maybe the joke was on us. User input should always be absolute top priority, and if that means something else has to stop then so be it. (Although with 24 cores...)
- speedplane 8y agoTo your point, I also remember working with early windows systems and when the network went down for a moment, the mouse and screen would freeze. Given the two options, Most would probably take the Mac.