4 ms·
One of the big ideas in BeOS was a thread per window, or even perhaps a thread per view. This helped realize a lot of the cool BeOS demos where multiple windows
by diskzero 5y ago
One of the big ideas in BeOS was a thread per window, or even perhaps a thread per view. This helped realize a lot of the cool BeOS demos where multiple windows were open playing videos, rendering OpenGL or otherwise keeping the CPU busy.
- zozbot234 5y agoThat's not really a good thing, though. You don't need "a thread per window" especially w/ modern async computation, you just need the UI to be in a separate thread from anything that might keep the CPU busy to begin with.
- dbt00 5y agoYes we've learned a lot in the last 25 years, and it certainly isn't a good idea, in retrospect, to have the C++ API for your GUI Frame object to extend the thread class. That said, in the days of single core, single event loop on all the major GUI frameworks (X11, Win32, Mac OS), it was absolutely a revelation about what was possible. The dovetails nicely with an earlier article about how quickly the pace of performance improvements felt magical in the early 90s, from the release of the 80386 to about 2010.
- sedan_baklazhan 5y agoBTW I think that OS/2 was NOT single event loop, right?