4 ms·
It was my general impression that porting Java found native threading bugs in multiple OSes. How stable or portable were native threads before that?
by skybrian 8y ago
It was my general impression that porting Java found native threading bugs in multiple OSes. How stable or portable were native threads before that?
- ChuckMcM 8y agoThis was 1992 and Posix, BSD, Microsoft, and a contingent from HP/Apollo were all putting forward ideas about what the API to 'threads' should be and even whether they were a "kernel" thing or a "user level" thing. Arguments were made that lightweight processes were the abstraction to use but as I recall that impacted portability. So yeah, they were pretty new and they were blowing up things left and right. Sun at the time had a leg up on most (if not all) UNIX vendors with a threading model that worked well. But it made porting the JVM harder and green threads lived for a long time as a fallback.
- vbezhenar 8y agoHow user level lightweight threads were supposed to utilize multiple processors?
- LoSboccacc 8y agoassuming the question implies "without using threading" - spawn multiple processes and migrate fibers across them as needed. of course it's not something a developer might want to do, but might be done as part of an user-land library. no idea why one would want that today outside of highly specialized code, but it might be that it could be more portable to other kind of non-preemtible system (i.e. os with fixed time sharing)