It’s been long time since my latest post, and i wanted to say something about GoBe, but this can be applied to the Refraction thing as well. I think resurrecting a software like gobe productive, is more than an hazard. If the software will be developed closed source, apart from the fact that developing isn’t cost-free, there’s risk that what happened at Be times, will rehappen again. Just think of a unexpected thing happening and blocking the development. Even if the source code gets open sourced there are a number of factors to consider :
- Backporting from windows is painful, expensive and need really a lot of motivation
- Backported code will be probably shitty and incomplete (see Titan, it's impossible to continue developing it).
- Are we sure then the app will be continued to be developed? There are hundreds of BeOS apps open sourced and just a fraction is continued to be developed, and usually this is done by someone which is part of the original team.
My suggestion is to rethink very well the real value of code. This should be seen with a long view on the future, to create an app comparable to MS Word or OpenOffice the investment is inestimable. Do you think the Haiku community have any force to create or develop a product comparable to the ones i mentioned? And we may want to talk about the interface_kit, do you think it’s ready enough to support so advanced features itself? Yes, LibreOffice/OpenOffice is big, it needs lots of dependencies, but if you take paper and seriously do an analysis on this, after the sum you’ll figure out that resurrecting a thing like GoBe will be fruitless and expensive at the same time. The same apply for Refraction, altough i’ve doubts on the code quality (basing on what i’ve seen in BeAE), do you think a $30’000 bounty wouldn’t be enough to have a decent port of GTK? No offense to anyone, it’s just how i see it, but translators aren’t really a good motivation to invest thousands of bucks into a new project, IMHO.