Welcome to embedded...
Posted Apr 3, 2009 7:56 UTC (Fri) by forthy
In reply to: Welcome to embedded...
Parent article: Android and Open Source (ABN)
IMHO, "pushing upstream before the product is released" is the wrong
answer to this question. Just develop in the open, i.e. in a public
accessible VCS. You can't guess when the release of the product is going
to happen, because there will be development all the time - as long as
you don't announce "feature freeze" or something like that. You don't
have to. When you do feature freeze, you create an internal fork, which
is not visible, and you forward-port your remaining bug fixes to the
external fork (which can continue to develop at the usual pace).
It looks like Google just has to learn how to do that sort of
development. Apple had to learn that, too. An awful lot of managers sleep
better when all the stuff they do is strictly confidential, no matter if
there is any real benefit. There had been rumors that the toilet paper at
Intel have "strictly confidential" written all over it ;-).
The main criticism I have on Android is rather different:
- You can't distribute native applications, you can only use their
JVM, which limits what you can do.
- The JVM is interpreted rather than using a JIT. This means
applications take more energy to run than necessary.
to post comments)