Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Communications Businesses Google The Internet Software Java Programming

Google, Sun Headed for Showdown Over Android 124

narramissic writes "There may be trouble brewing between Google and Sun. Google has written its own virtual machine for Android, 'most likely as a way to get around licensing issues with Sun.' If Google used any of Sun's intellectual property to build Dalvik, Sun could sue Google for patent infringement. But here's where it gets interesting - Sun is a vocal advocate for open source and it would 'hardly appease the open source community to sue Google over an open source software stack.'"
This discussion has been archived. No new comments can be posted.

Google, Sun Headed for Showdown Over Android

Comments Filter:
  • To put it bluntly. (Score:5, Insightful)

    by LWATCDR ( 28044 ) on Friday November 16, 2007 @11:27PM (#21386971) Homepage Journal
    So reporter thinks that Sun might sue Google for forking Java all the while over looking the fact that Sun has GPLed Java and that other groups have produced versions of Java with out getting sued. Google and Sun both are saying that they are working together.
    In other words a none story.
  • by mhall119 ( 1035984 ) on Saturday November 17, 2007 @12:03AM (#21387177) Homepage Journal

    Java on web browsers has possibly gotten worse with years.
    Java 6 update 3 contains improvements to both install and startup of the JVM within web browsers.

    Current multi-media web dev is relegated to Flash, but I'm sure that there are many skilled programmers out there that would be glad to have a lean Java VM & API working in web browsers. Sun gave up long time ago, Google could take over and make it ubiquitous.
    A new spec for easily embedded media components is in the works, hopefully it will make it into Java 7, and will be a good compliment to Java FX script on the web. There is talk about plugging it into existing media frameworks like GStreamer or VLC, to bring in all of their supported formats. Sun may have deglected multi-media, but it's not quite forgotten yet.
  • Ahhhh, Slashdot (Score:5, Insightful)

    by ZombieRoboNinja ( 905329 ) on Saturday November 17, 2007 @12:07AM (#21387187)
    Title: "Google, Sun Headed for Showdown"
    Summary: There MAY be trouble brewing between Google and Sun...
    TFA: Google COULD get in trouble with Sun, according to some analyst (but both parties declined to comment)
    Reality: Move along, nothing to see here...
  • it's a real issue (Score:3, Insightful)

    by m2943 ( 1140797 ) on Saturday November 17, 2007 @01:28AM (#21387531)
    while over looking the fact that Sun has GPLed Java

    Releasing software under the GPL wouldn't give Google patent rights, since Google is not basing their software on Sun's.

    and that other groups have produced versions of Java with out getting sued

    Quite to the contrary: all conforming Java implementations that have ever been produced are produced under license from Sun, and Sun has used legal threats to ensure that.

    There are a bunch of non-conforming implementations where Sun has chosen not to press the issue yet, but that doesn't tell you that Sun doesn't have the patents or doesn't enforce them. And, if you look at USPTO, you'll see that Sun has dozens of Java-related patents, some of them on fundamental aspects of the platform like bytecode verification.

    OTOH, I suspect Google was careful about this, and this is one of the reasons Google didn't use a standard JVM. In the end, all Android shares with Sun Java is a fairly generic programming language and some fairly generic core APIs.
  • by cromar ( 1103585 ) on Saturday November 17, 2007 @01:46AM (#21387603)
    It's not the CEOs. It's the PR and legal depts.
  • by Actually, I do RTFA ( 1058596 ) on Saturday November 17, 2007 @03:30AM (#21387979)

    GuI interfaces are usually done horribly in Java, because its easy to screw them up. The unresponsive Gui (see zend framework) often makes people think that Java is slow.

    Unresponsive is slow. From a user's (and my) POV, I don't care if code executes in 10ms or 299ms if the GUI refreshes every 300ms. Why, because I use a program to do things, not to marvel at the effiency of the algorithim (unless I'm examining the code).

    Additionally, a lack of progress bars leads to killing processes and restarting them, making them slower in reality.

If you have a procedure with 10 parameters, you probably missed some.

Working...