Forcing a developer to use multithreading, which is pretty complex for most programmers to code for, it is the wrong way to go for an OS. There was some controversy about this, but at the end, the experienced programmers agreed. And Maarten Hekkelman, of the Pepper fame (Maarten is also the same person who wrote the BeOS debugger when he was hired by Be to do so), seems to agree too: There won’t be a Pepper for BeOS, just because the BeOS design does not make it easy to code such a big and complex app. Before you start replying in this story, make sure you read all the comments here. Our Take: I love BeOS, but BeOS is not perfect. In fact, what Be’s marketing was trying to sell as the best feature of BeOS, pervasive multithreading, it is also its most weak spot. Now you know why big apps crashing too much under BeOS, and why there are not many big apps available anyway. Too hard to code big apps for such an environment, for most developers. Take Scooby for example. This person’s multithreading code, is far below par, and mind you, Mr Takamatsu is an experienced developer. Scooby still crashes too much though and locks up the app_server at times, in a spaghetti multithreading confusion… Same goes for Gim-ICQ and lots of other apps.Update: Maarten Hekkelman responded to our comment section explaining his decision and Pepper’s design.