Re: RIP BeOS
You are not wrong about BeOS being harder to program for due to the multithreading.
The real shame is that back then, people saw that MT is tricky and avoided doing it, so BeOS fell, but now it seems every halfwit thinks they know how to MT under Windows and Linux and have no qualms about inflicting the results on us.
Cue flashback to my team leader asking for a sanity check after seeing the expensive contractors' code create a Mutex as a local variable, strangely always succeeding in locking it on the next line of code. Something that worked so well said contractors decided it was a Pattern and duly cut'n'pasted it... Well, it passed *their* tests, never deadlocking.