Linked by Thom Holwerda on Thu 4th Mar 2010 13:12 UTC, submitted by Infamy
Thread beginning with comment 412356
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 raised another question I've been pondering for a while. Anyone knows why they feel it is so important to be backward-compatible with BeOS?
For one, it provides a limited scope at least. It prevents people from arbitrarily expanding the API/ABI and instead focus on making the system just work properly, as well as, and even better than BeOS did.
How many programs written for BeOS actually has any meaning today? Aren't they all dated by now in one way or another?
There was at least one closed-source library that a few apps still use, Marco's liblayout (http://bebits.com/app/3363) it is used in SoundPlay and Wonderbrush, and likely some other apps that are still useful.
I suspect Wonderbrush will eventually be migrated to Haiku's built in layout kit system (which is unfinished, and the public API hasn't been solidified yet). I gather there still isn't a replacement for SoundPlay that is nearly as awesome... and only an older version of SoundPlay runs on Haiku due to the use of some private API from BeOS...




Member since:
2008-11-27
This raised another question I've been pondering for a while. Anyone knows why they feel it is so important to be backward-compatible with BeOS?
How many programs written for BeOS actually has any meaning today? Aren't they all dated by now in one way or another?