This is not helpful. The question implies that with a few
tweaks, like
changing the names and SSO, Android might be
able to come into compliance - ie:
not infringe Oracle's
precious anymore. So if you say...
"You _can_
obviously do this, you would even have the
same functionality, but nobody would
expect it."
"You _can_ obviously do this" ...is not a good answer,
because you cannot do that. You cannot tweak Android
by simply changing
the names and SSO.
"but nobody would expect it." ...is not a good
answer.
"nobody would expect it" is a trivial side effect that
misses the
point.
The real effect is you would have to write a whole new
language
and rewrite Android from scratch. You will not have
the same functionality,
because one of the functions of
Android as it is now is compatibility with
Java. This was
one of the fundamental design choices - "Create a language
that
is compatible with Java". Your new language will be no
longer compatible with
Java. It will be a different
language.
"But if you want to provide a
java language, you better
provide the basic classes/APIs otherwise programming
would
be very confusing."
Again - "very confusing" is a trivial side
effect. Not
just confusing - programming in Java would be impossible!
Without
the basic classes/APIs, whatever you use is simply
not Java. [ Reply to This | Parent | # ]
|