3 ms·
Because of the application barrier. It's a chicken and egg problem, nobody wants to use an OS without applications and not many want to develop for an OS that n
by JohnStrange 10y ago
Because of the application barrier. It's a chicken and egg problem, nobody wants to use an OS without applications and not many want to develop for an OS that nobody uses. To get it started, a lot of resources and power (e.g. quasi-monopoly or tons of money) is needed, or you need to have some binary compatibility with another OS. The latter is difficult due patents and copyright, and because it will likely make applications slower than on other platforms.
Apple was able to do it, because they sell hardware, not software, but the transition from Classic OS to OSX was hard and rocky even for them and could have failed.
It's a pity, because neither Unix/Linux clones nor Windows are really good and technically sound desktop operating systems from a modern perspective, and it would be possible to develop something way better. As for mobile, I don't know, it's a different thing.
- JonathonW 10y agoApple was able to do it, but not without both a compatibility layer for direct binary compatibility (Classic) and a migration path to allow the same source code to be compiled for both OS 9 and OS X (Carbon). Not to mention the heavy Java push they made for a while, which didn't end up becoming much in the long run but did provide one more way for developers to get their applications onto the platform. And developers like Omni that followed NEXT after their purchase by Apple.
- pjmlp 10y agoThe Java push was mainly driven by the uncertainty of Objective-C's adoption. Once it was clear developers were ok with using Objective-C, Java Bridge was shown the door.