I just saw the Gobe/BeOS story on OSNews.
It is true that Gobe and BLG have a distribution/development deal in India and China, much of the rest of the story is misleading.
GobeProductive is not going to buy BeOS. First of all the developer of the software is Gobe Software, Inc. GobeProductive is the name of the product. Just to make things more confusing, the software was distributed by a company called Gobe Corp for several years. Gobe Software, Inc has reacquired the software and is exploring several paths to further development and distribution. Currently the Gobe.com website still reflects this distribution arrangement with Gobe Corp. That should change soon.
If there is any activity, or purchase of the source code to BeOS it will not be instigated by Gobe Software, Inc. However, what BLG and its partners in India do is another story; I can't speak for them. I am not going to comment on this further however.
I am not at liberty to discuss any roadmap plans for GP, but there is no plan to do anything with Java in the codebase. GobeProductive is 100% a C++ codebase and will stay that way. We do have a version of the software that runs on Linux, but it was never taking to shipping quality. If we pickup and continue with a Linux team, it will probably be via a port of the code to KDE and that would get us most of the way to a Mac version as well.
The GobeProductive codebase is a remarkable platform and I hope that BLG's marketing plans in India will allow funding for much more development of the software.
Bruce Q. Hammond
CEO, Gobe Software, Inc."
posted by Thom Holwerda on Wed 23rd Jan 2008 07:04 UTC
Yesterday we reported on GoBE
Productive Software (I knew that) returning to the market with a new version, backed by an Indian firm. In addition, the source article claimed GoBE Software was closing a deal on buying the BeOS operating system from what can only be Access. During the night (as in, CET) Bruce Hammond, CEO of GoBE Software, sent me an email with a few clarifications, and I have the permission to reprint that email below. Read more for the email.