| The task is too huge, BeOS
has been in development for 10 years now Be has not been 30+ engineers big for 10 years, only in the 5 last years, plus they spent much time on design, which we'll save by "copycat'ing it (for the sake of the community) plus we'll re-use some code (Linux..) at least at the beginning; anyway just look at AtheOS: it demonstrates what you can do in a (_relatively_) short time if re-using to the maximum some external code out there and doing some external code out there and doing trade-offs that can save you some time.. Just imagine where AtheOS would be now if worked on by 5 or 10 people, with the clear goal of being source compatible with BeOS's API? This seems very much to be the rationale behind openbeos, blueos ..etc" If you succeed, you will kill BeOS! are you stupid?! In fact, we believe that if developers use the BlueOS API, to compiling/porting the applications to BeOS will be easy. Both APIs will be similar; BlueOS will add some features that can be ported on BeOS quickly. For starters, BlueOS applications will developed on BeOS while BeOS compatibility is incomplete. Why is BlueOS NOT under a GPL license? The development of an OS must be managed, otherwise a lot of duplicated works or mistakes can be easily made. But to not be in violation with the GPL, parts of the OS will be under GPL. I've be deceived as a user and developer once with BeOS (and even twice if you count the Amiga), losing all I had done when the mothership went to bankruptcy.. why would I trust you/BlueOS even though you're not Opensource? We're a different kind of "mothership": we're not money-driven, no investors dictating us what we have to do, it's a labour of love done in our spare time (we all have day jobs (software engineers)) so the only reason we'd have to stop i)) so the only reason we'd have to stop it is loss of user interest. We won't end up the way Be and Amiga did, frustrating users who wnted the story to go on, we'll only end if there are no users left who want us to! How to join us? If you think that you can help, follow this link. After, write us a mail with you name, age, job, interest, what you can do for the project and write a first document (in HTML if you can, to add it in the member area). A mailing list is already open, you will be subscribed to discuss about your work. Who are you? Soon, we will add on the site the list of members. Today, we are 5. How do you think to go through the limitations of current linux filesystems? (no indexing, etc) We can abstract the idea of FileSystem and only send queries to a server which will manage the indexes, by using global index tables and file resources (implemented by .rsrc or .info files...). Multi-screen? Yes! A new button on windows will appears to easily jump windows on a different workspace or an other display (possibly on another computer). A nice menu with a list of preferred displays could be nice... Former Be Engineers in the team? With the recent changes in the Be Inc. team, a lot of useful knowledge is out of Be Inc. - geniuses are free ;) |