2 ms·
"BeOS approach to multithreading was really just a dead end. Nobody does multithreading that way anymore." I was about to start digging up more on its multithr
by nickpsecurity 11y ago
"BeOS approach to multithreading was really just a dead end. Nobody does multithreading that way anymore."
I was about to start digging up more on its multithreading due to interesting things I read in architecture documents. Not to mention their multimedia demos. Read lots of positive stuff with interesting tricks like "benaphores."
So would you clarify why you think it was a bad design and why nobody will use it any more? And did their concurrency or other design efforts get anything right in your eyes?
- rvense 11y agoI programmed for BeOS a little (mostly before I really understood programming, though), and what I remember is just the shear number of threads. Each window (maybe even subregions of windows, don't remember) would spawn two, I think. You'd have to lock to do the simplest things. A lot of rote, manual management of shared mutable state.
- nickpsecurity 11y agoI got you. So it's not tge architecture or how threading worked under hood but the developer experience the API's forced was bad? Right? That could be fixed easily in a knockoff.