Oracle: Google Has "Destroyed" the Market For Java
itwbennett writes: Oracle made a request late last month to broaden its case against Android. Now, claiming that 'Android has now irreversibly destroyed Java's fundamental value proposition as a potential mobile device operating system,' Oracle on Wednesday filed a supplemental complaint in San Francisco district court that encompasses the six Android versions that have come out since Oracle originally filed its case back in 2010: Gingerbread, Honeycomb, Ice Cream Sandwich, Jelly Bean, Kit Kat and Lollipop.
It's a shame Pamela Jones shuttered Groklaw ... her insight into this case would have been invaluable.
We need to stop the dangerous idea that interfaces can be copyrighted before it becomes as much a bane on software as software patents were before Alice vs. CLS Bank.
vi ~/.emacs # I'm probably going to Hell for this.
Because J2ME was such a brilliant mobile platform.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Oracle (then Sun) could have created an operating system for mobile phones based around Java. But since Google did, they want to profit off of it? They should go to hell.
Java was never useful on phones until Google built something decent.
Sun/Oracle could never build a decent phone with Java, no matter how much money they pumped into it.
If you work somewhere that uses Oracle products or is considering an Oracle product, fight to the bone to get their shitware tossed out.
We need to end this company, it's a tumor in the software ecosystem.
Mod me down, my New Earth Global Warmingist friends!
irreversibly destroyed Java's fundamental value proposition as a potential mobile device operating system
Well there's the problem. Oracle thinks the language and runtime are a complete operating system. There's nothing stopping Oracle making a different OS that uses Java. In fact, the vast amount of libraries for Android out there should be easy to port. Next we'll hear how Microsoft destroyed the value of C as used to build an OS.
Java...[garbage collection] is the .[garbage collection] best .[garbage collection] programming .[garbage collection].[garbage collection] language for .[garbage collection] mobile devices .[garbage collection] .[garbage collection] because it is .[garbage collection] faster .[garbage collection] then C++ and .[garbage collection] more .[garbage collection].[garbage collection].[garbage collection] deterministic and .[garbage collection] .[garbage collection] .[garbage collection] nev .[garbage collection] er .[garbage collection] drops .[garbage collection].[garbage collection].[garbage collection] user .[garbage collection].[garbage collection] input.
I like Java .[garbage collection] becuase .[garbage collection].[garbage collection] it's write .[garbage collection].[garbage collection] once, .[garbage collection].[garbage collection].[garbage collection] and it runs .[garbage collection] .[garbage collection].[garbage collection] provided you have all .[garbage collection].[garbage collection].[garbage collection] the libraries, the .[garbage collection].[garbage collection].[garbage collection] correct java interpreter .[garbage collection].[garbage collection].[garbage collection] and enough .[garbage collection].[garbage collection]
javax.servlet.ServletException: Something bad happened
at com.example.myproject.OpenSessionInViewFilter.doFilter(OpenSessionInViewFilter.java:60)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.example.myproject.ExceptionHandlerFilter.doFilter(ExceptionHandlerFilter.java:28)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.example.myproject.OutputBufferFilter.doFilter(OutputBufferFilter.java:33)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: com.example.myproject.MyProjectServletException
At first, I read that as "Oracle Has 'Destroyed' the Market For Java"... which, of course, seemed quite plausible.
RIP SUN
I have no special gift, I am only passionately curious. --Albert Einstein
Does anybody feel sorry for Oracle???
The contenders for biggest enemies of Java are:
1) Micro$oft - Effectively killed the JavaBean web plugin market with their own lackluster JVM via EEE (Embrace, Extend, Extinguish).
JavaBeans is the technology that has the biggest negative view on the net and rightly so. If Microsoft had not done such a good job killing it, Java would likely be in a different light today as more energy would have been spent making JavaBean libraries better while the real engineers at Sun still had control of the source.
2) Oracle - They just do not get open source or anything that came from Sun.
Google has popularized Java way more than Oracle could ever imagine.
"You don't anthropomorphize your lawnmower, the lawnmower just mows the lawn, you stick your hand in there and it'll chop it off, the end" - B. Cantrill
Sun destroyed the market for Java.
Sun wanted to sell hardware, and they designed Java to run well with their hardware. Sun's ideal was the network is the computer. Java is/was a client language that could run on a lot of platforms, with in Sun's mind a Sun server at the other end. Didn't quite work out that way. Sun was going belly up, Oracle bought the carcass. Sun gave Java away. You can't put the jinni back in the bottle.
Java was worthless when Oracle bought Sun. They're engaged in revisionist history trying to milk a dead cow.
The tech industry, just like every industry, improves as people discover new and better ways to do things. If you can't keep up Oracle, you fall behind. And since you've chosen to litigate instead of innovate, you have fallen behind.
No one is guaranteed profit.
Be seeing you...
Yes, and what exactly did Sun do with that?
Oh yeah, there is JavaFX, which still requires an OS to run on
That is where the disconnect is
Wherever You Go, There You Are
Java is a programming language, not an operating system. Examples of operating systems are Linux and Unix.
Nothing could have "destroyed Java's fundamental value proposition as a potential mobile device operating system" because the value proposition of Java as an operating system is zero, and always has been. It's like the value proposition of an orange to be an apple.
Oracle's nonsensical claim might be merely a case of lawyers or managers showing their ignorance of the computing subject domain or just being sloppy with their terminology, which is not uncommon. However, it gets worse.
A proprietary software package may have a calculated expectation of market share and profit if there is no competition, but this is not the case with programming languages because they always have competition from countless other languages. It is especially not the case with open source programming languages because they typically enjoy multiple implementations, and these make captive markets almost impossible to maintain.
It seems therefore that Oracle's market expectations were based on a flawed analysis.
That mistake would have made any market expectations unsafe, but any expectations were dealt a further blow by Oracle's highly abusive attempt to copyright SSO in their litigation against Google. This must have alienated practically everybody who knows anything about programming, and the likelihood is high that many Java programmers who had other languages available must have abandoned Java like the plague to avoid potential SSO copyright liability.
In other words, if anyone killed off interest in Java, it was probably Oracle themselves.
"The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
In general, no. Unfortunately, Oracle owns the rights to Java. That means that Google must comply with Oracle's terms within the limits defined by law. Doubly unfortunately, that means that everyone with a vested interest in the situation is going to have to watch a drawn out soap opera as the case winds its way through the courts.
Oracle are the ones that have destroyed Java since nobody trusts Oracle and their licensing.
If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
What legal battle with Microsoft? As the OP already stated, Microsoft has put C# out there for 3rd party implementations with a legal guarantee not to sue.
sony-e had a working prototype all java(with I suppose their own os underneath). basically android was a clone of that.
but what sunoracle fucked up in the mid 00's was being too slow in developing j2me extensions(and the 'all java' phone os that they kept in different projects for years and years) and just badly managing how they could be used(four security dialogs for creating a file in a folder on the sd card each with two clicks from the user, for example - NO MATTER WHAT SIGNING YOU PAID FOR), thus the market for android was there when android emerged.
as for j2me, the process a new API went through to be an approved API was just stupid. the end result was api's that had always some flaw on them or were just unusable from the day 1, like the j2me 3d _scene_ descriptor shit, which was just a wrong, wrong way to go about it on the hw and use it was launching for(like, the api might have been ok for making some animation suite or whatever, but shitty for making games).
there was a market for a java development based smartphone os all right.. they just dragged their feet on it for way too long, so that market hole is now filled with android.
they just didn't care about it enough to make sure that the shit they were certifying and dictating how it should be was usable at all.
world was created 5 seconds before this post as it is.
Is that why Java rules the enterprise and Microsoft is relegated as a distant outsider? Java pretty much dominates enterprise development. C#? Not so much. Just ask the London stock exchange for experience with Microsoft and C#.
Since the London Stock Exchange switched to Linux/C++, your comment is irrelevant to this discussion.
http://www.computerworlduk.com...
So we ended up using another VM called Skelmir which was a clean room Java, roughly analogous to Java 1.5 SE albeit missing some stuff mostly in the javax & sun namespaces. Performance was better, it was cheaper and it was possible to develop normal Java code with a reasonable expectation it would work on the STB. I'm sure the same sentiment was felt everywhere. Companies resented being charging an arm and a leg for a piece of shit runtime which was barely fit for purpose.
As for why Google succeeded where Oracle failed... It's because they offered more or less a full Java SE API and a rich mobile API that allowed developers to write apps without making compromises. It didn't really matter that the byte code was compiled into something else because they also provided excellent tools that integrated with Eclipse to take care of all that.
I don't believe for a second that if Google hadn't used Java as their API that Oracle would have triumphed. Not in the slightest. If anything Google did Oracle a favour by using their language and therefore keeping it relevant for portable devices.
That means that Google must comply with Oracle's terms within the limits defined by law.
But Google doesn't use Java, they use Dalvik/ART, which aren't written by Oracle and therefore don't have Oracle's ToCs attached to them.
They do happen to be compatible with Java, but if you are allowed to copyright APIs (which is what Oracle are pushing for) then that would be absolutely insane for the IT industry, as you wouldn't be able to implement an API (or possibly even access an API) without the permission of whoever wrote that API.
They didn't make something that worked similarly to Java - that would have been OK, C# is similar to Java after all. They made something that was *identical* to Java. If they didn't want to be sued they should have made their own API and their own language
What it comes down to is should APIs be copyrightable. Google created their own implementation of the Java API, if companies are allowed to copyright APIs then you can kiss WINE goodbye immediately, anyone wanting to implement an existing API would also be in trouble, and you might not even be able to create a program that even accesses an API without explicit permission.
To come back to your metaphor just because something implements the IDuck interface doesn't mean it's the same kind of duck.
You can install an APK without that. Blame the developers for not releasing free apps directly as an APK.
In that case, it's no different than Windows 8 or 10 or even OS X. There's an app store, but you don't have to use it.
but if you are allowed to copyright APIs (which is what Oracle are pushing for)
You are allowed to copyright APIs. This case went through the appellate court, which ruled that APIs are copyrightable, and to the supreme court, which let that ruling stand.
The case has moved on, and is now trying to determine if Google has a fair use defense. But there is no doubt that APIs are copyrightable under current law.
"First they came for the slanderers and i said nothing."