Authored by: bugstomper on Saturday, May 05 2012 @ 08:59 PM EDT |
[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Saturday, May 05 2012 @ 09:11 PM EDT |
The primary reason for maintaining compatibility with the Java API's were to
allow Java programmers to port their existing applications over to Android
fairly quickly without having to change every API call. Additionally, have
familiarity with the Java API's also allowed you to develop more quickly, but
this is debatable as adjusting to new API's isn't really that difficult nowadays
with the code completion tools most IDE's ship with.
Google doesn't call their version Java so how does Oracle even have a leg to
stand on? Had Google called their implementation Java then there would have
been an issue, but they don't so why are we here again? This is simply a last
ditch effort from Oracle to try and extort money from Google by preposterously
claiming that method declarations fall under copyright. This is not only a
despicable maneuver, but it goes against the moral conscience of every
programmer. Any programmer that works for Oracle must truly be disgusted with
what they're trying to do.
Oracle is trying to do what SCO did and they failed miserably. History shall
repeat itself again. It does make me wonder what would happen if Oracle did
with the copyright case because it would give IBM a clear road to shut them down
for using SQL without a license and that would truly be a sweet victory.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Saturday, May 05 2012 @ 09:13 PM EDT |
Question and answer run together
Tufty
[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Saturday, May 05 2012 @ 10:06 PM EDT |
. [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Saturday, May 05 2012 @ 10:12 PM EDT |
. [ Reply to This | Parent | # ]
|
|
Authored by: Gringo_ on Sunday, May 06 2012 @ 12:10 AM EDT |
Incorrect. The issue is whether Google could
do that. See my
comment down below.
[ Reply to This | Parent | # ]
|
|
Authored by: Gringo_ on Sunday, May 06 2012 @ 12:12 AM EDT |
See my comment down below. [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Sunday, May 06 2012 @ 10:09 PM EDT |
FYI: Many devs I've talked to are ALREADY pushing to move away from Java at the
least (its C like syntax make this easier than you think; I can 'compile' Java
code into C++), and at the extreme some have made the migration from Oracle's
DBs to PostgreSQL and vow never to use their services again (specifically citing
this case as the cause). Others still await the outcome of the case.
I myself, a language designer & implementer, won't just stand by idly
getting shot at until a bullet strikes me before I decide to act -- Oracle's
intent is known whether or not they hit the mark. Even if they fail, that was
too close for comfort. I've ceased my contributions to Java platforms, and am
shopping around -- (Perl6 Parrot looks fun).
So, for some, it is already too late for Oracle to do the right thing -- that
time was before firing off this suit -- to others it may not be too late for
them to change.
However, there IS ALWAYS a point at which it's just too late, nothing you do
will matter beyond this point.
As as example: It's too late to change if a robber swears they'll stop burgling
after the next house, and is shot dead as a thief.
Alternatively: "it's already too late"[ Reply to This | Parent | # ]
|
|