4 ms·
I 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 (ma
by rvense 11y ago
I 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.