Linked by Thom Holwerda on Sun 9th Sep 2007 18:08 UTC, submitted by koki
Permalink for comment 269943
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2005-07-06
I am wondering what examples he has too. Every program that seems to have problems under BeOS appear to be ports of single threaded programs.
Since the code was never multi-threaded in the first place, hacking it to work under BeOS tends to expose design decisions of the original code.
I have not seen any such problems with programs written proper for BeOS except for 'DriveSetup' which always act weird to me.