Linked by Thom Holwerda on Fri 7th Sep 2007 19:38 UTC, submitted by koki
Thread beginning with comment 269674
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
This is an excellent article. I learned to write code on BeOS, so I consider myself pretty spoiled, API-wise. The multithreaded nature of the OS doesn't really pose that many problems, but beginners or those who started on other platforms will find this a tripping point unless they already have this kind of experience (not as common as you might think) or they are given some sort of introduction like stippi has graciously done. Fine work, if you asked me. 





Member since:
2006-01-26
I mean, no offence but anyone coding an OS should be completly familiar with at least those common problems and solutions, don't you think ? In fact I don't really see the point here.
This is basically an article for new developers who are considering writing applications (for Haiku), not the underlying OS. If Haiku's application base is to grow any time soon, it seems like a little education on how to write good multi-threaded apps would be in order, no?
One of the things that has "plagued" BeOS/Haiku application developers for years is the unavoidable multi-threading development model. It is a barrier that can prevent newbie developers from quickly writing good BeOS/Haiku software.