|
|
|
| Authored by: Anonymous on Sunday, May 06 2012 @ 01:10 PM EDT |
The question is not could they have come up with their own SSO and still use
Java.
The question is could they have come up with a new SSO/names, kept the methods
and made programmers learn a new vocabulary. (which may not necessarily be
'Java')
The answer to which is yes they could and the result would not be Java.
There is no valid reason why Google could not have renamed Object as Root and
replaced Class with Thing and make every Dalvik Thing extend from Root rather
than Object
(there are many valid reason why they did *not* do that, but that is beside the
point, it still remains true that they *could* have done that, cf the point near
the end of my post, you can do everything, some things are just not very
sensible.)
I acknowledge that some of the names are likely to be the same or very similar,
but that is not the issue, the key is to destroy the SSO, it is only the SSO
that is being asserted, this can be achieved by simply flattening every one of
the 400 classes (whatever you choose to call them ) into a single library with
no subsections..
What you would get would no longer be Java and nor would it contain the SSO, and
many aspects of the toolchain/platform would have to be redone, but it *can* be
done.
I do not wish to argue with you, but I am not wrong, and I do not think you are
properly considering the points I have put forward in their full context,
[ Reply to This | Parent | # ]
|
|
|
|
|
