Slashdot Mirror
Will Pervasive Multithreading Make a Comeback?
exigentsky writes "Having looked at BeOS technology, it is clear that, like NeXTSTEP, it was ahead of its time. Most remarkable to me is the incredible responsiveness of the whole OS. On relatively slow hardware, BeOS could run eight movies simultaneously while still being responsive in all of its GUI controls, and launching programs almost instantaneously. Today, more than ten years after BeOS's introduction, its legendary responsiveness is still unmatched. There is simply no other major OS that has pervasive multithreading from the lowest level up (requiring no programmer tricks). Is it likely, or at least possible, that future versions of Windows or OS X could become pervasively multithreaded without creating an entirely new OS?"
I'd be interested as to why you were asking "BeOS the company" for support on a Be, Incorporated product, but that may be why you got little support.
The error dialogues you describe are not possible under BeOS - as a daily user since the turn of the century, there is absolutely no component of the system that gives errors in that format. Every error dialogue allows you access to a debugger, and the OS components are not symbol stripped. All drivers and system components put large amounts of data to the syslog, which, had you contacted technical support correctly, you would have been told how to enable - its a boot-time option.
As goes the support level, I and thousands of other users never had those problems.
Can I suggest you've managed to acquire some false memories here?