Standards Page - The Development of BeOS Standards

Initially, Be tried to utilize another OS for the BeBox. Due to costs and compatibility issues, this plan fell through, and the development of BeOS began. At each step of the way, BeOS encountered roadblocks that forced Be to develop customer software. Everything about BeOS, from the kernel to the keyboard software, was written custom for the BeBox.

UK based? Has your car been impounded for lack of insurance? ? You may need some impounded car insurance.  Facing disqualification from driving? Check here for information about penalty points

Since the development of BeOS, various software standards have come and gone. The original developers of BeOS were all refugees from Apple, and consequently many of the standards they initially utilized were brought from the current versions of Mac software. All of this had to be changed when AT&T abandoned the Hobbit processor line and Be had to adapt to the PowerPC processor architecture.

Under PowerPC and later x86, BeOS grew more and more standardized, at least with itself. The problem many users faced was that the BeOS standards were their own. Applications would need to be created and compiled specifically for BeOS and did not work between other operating systems.

Haiku, today, has adapted to more open-source standards. It still occasionally has trouble with some hardware or software compatibility, but the Haiku development team is able to solve many of these problems.

Copyright 2013 All Rights Reserved