3 ms·
Haiku was stuck on old GCC only because they wanted to support old BeOS binaries? But binary backwards/forwards compatibility is not requirement for many use-ca
by zokier 3y ago
Haiku was stuck on old GCC only because they wanted to support old BeOS binaries? But binary backwards/forwards compatibility is not requirement for many use-cases.
- pjmlp 3y agoHaiku without the BeOS applications wouldn't have that much to show. This is the way to go on platforms that favour shipping binaries instead of source code. Outside Linux/BSD, stable ABI across OS versions is a concern, hence why Apple, Google and Microsoft platforms all offer ways to keep this going.