[openbeos] R2 on our machines before R1

  • From: "Solaja, Zenja" <solaja@xxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Tue, 24 Sep 2002 13:13:23 +1000

<taken from OSNews and the article by Daniel Switkin>
I have a strong feeling that OBOS R2 will arrive before R1. Why? It is
common knowledge that the last 10% of code takes 90% of the developers time.
Once OBOS is close enough to working, it will get compiled with GCC3.2+ and
be called R2, with lots of open-source apps targeting it. It wont officially
be called R2, but thats how it will be known amongst the community. I think
even OBOS teamleaders will realise that it's not worth the effort of
spending more time on R1 to get the last 8-10 closed source apps working,
especially not once we've got OpenProductive and Mozilla to work on R2. So
binary compatibility will be foregone, in order to move forward. Wasn't that
the BeInc philosphy, remove the cruft, the old bloated binary compatible
sludge, and start fresh. BeInc broke binary compatibility with almost every
major release.

Hmm, there seem to be a lot of BONE and Dan0 only apps on BeBits lately.  I
have a feeling the same thing will happen with OBOS - R2 will be
unofficially out long before R1 (R2 being the Gcc3.2+ binary incompatible

Something to consider, perhaps.

This email is intended only to be read or used by the addressee.
The information contained in this e-mail message may be confidential
information. If you are not the intended recipient, any use, interference
with, distribution, disclosure or copying of this material is unauthorised
and prohibited. Confidentiality attached to this communication is not waived
or lost by reason of the mistaken delivery to you.

If you have received this message in error, please delete it and notify us
by return e-mail or telephone Aristocrat Technologies Australia Pty Limited
on +61 2 9413 6300.

Other related posts: