Linked by Thom Holwerda on Tue 3rd Apr 2007 22:39 UTC, submitted by El-Al
"We are very pleased to announce that Access, the current holders of the BeOS intellectual property, has responded positively to our request for permission to reproduce the BeBook and all the Be Newsletters. As a result, we will be able to release these BeOS legacy documents under a Creative Commons license."
Thread beginning with comment 227111
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2005-06-29
What about if Access would release BeOS source code? What is going to happen to haiku source code? Consequences in the psychology of Haiku's developers? Would we see a merge in the code trees?
The code trees are likely to be completely incompatible with one another. The difference is probably that between night and day. The end result might look similar, but I would be surprised to see even one chunk of code that is the same in both.
Sure, the Haiku devs could learn majorly from the code, but a merger? Don't think so.
Edited 2007-04-03 23:44 UTC
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
What about if Access would release BeOS source code?
What is going to happen to haiku source code?
Consequences in the psychology of Haiku's developers?
Would we see a merge in the code trees?