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.
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.”
Or all of the above… it seems there’s still more of the story to unfold from all the rumors: will the other company actually manage (or at least are trying to) purchase BeOS from Access, and what, exactly, is their aim?
It seems it’s all fork()ed up, and GoBe Productive is going away from BeOS/Haiku, and BeOS is… likely going away from Haiku, if it is going anywhere at all.
Even if they buy out the rights and code to BeOS from Access, I can’t help but think that Haiku will end up being the long-term winner of the contest for mindshare, at least in the rest of the world: it seems they (the other company) are looking perhaps to sell to the Indian market, and perhaps that’ll work well, given a pre-defined set of known-working hardware for a cheap system base. But, time will tell…
Thanks for posting this, Thom.
This is the first evidence of ISV recognition of KDE4. The work the KDE guys have put into the “pillars” of their new version mean companies like Gobe (plc/inc/corp/productive/etc) can target KDE as a base, and pretty much automatically get a Mac product also.
Great news Gobe is back, though I reserve any enthusiasm until I can see and test a killer product