How Oracle’s business as usual is threatening to kill Java
arstechnica.com
How Oracle’s business as usual is threatening to kill Java
1–10 of 48 posts
Re: How Oracle’s business as usual is threatening to kill Java
#2"It's a dangerous game they're playing,"
Not for Oracle it isn't.
Re: How Oracle’s business as usual is threatening to kill Java
#3How likely is it that Oracle could sue a company using Java? Are you safe as long as you don't create something Dalvik-like?
I have a gut feeling that lawsuit has had a chilling effect on enterprise Java usage. It obviously didn't put Oracle in a good light.
Re: How Oracle’s business as usual is threatening to kill Java
#4"It's a dangerous game they're playing," Not for Oracle it isn't.
It's more dangerous for Oracle than anyone else. You can only be a bully for so long before customers and potential customers become scared of you and go elsewhere. When you scare off customers, you die. I won't implement anything Oracle and my company for just that reason, they're unethical and a liability. Predatory licensing rules, lock in, stick it to the customer pricing, and the potential for litigation at the drop of a hat.
Re: How Oracle’s business as usual is threatening to kill Java
#5It seems like no sane people would choose Oracle for a new project. Is that a company milking its legacy contracts and buy new legacy product until they can't follow fast enough?
This kind of business model is a drag on the whole ecosystem, just like Microsoft as a monopoly stagnated the whole ecosystem until Linux broke out.
Re: How Oracle’s business as usual is threatening to kill Java
#6Is Java EE released under an open source license?
The article only makes sense if the license is not open source, but this important detail appears to have been left out entirely.
A few quick searches suggest Oracle is using some kind of free-as-in-beer license for Java EE.
edit: buried in the middle of the article is this passage:
> JCP concerns aside, rumblings over what's happening with Java EE have been much louder. Discontent began when Oracle shut down commercial support and internal development for GlassFish, the open source version of Java EE that served as the reference implementation for the platform. Even without commercial support, Open Glassfish was still being predominantly developed by Oracle employees. Java EE 7 and the GlassFish open implementation soon released on June 12, 2013.
So what's the problem here? Big company doesn't want to fund R&D for a product that generates no revenue?
Said product is open source, so community takes over.
Re: How Oracle’s business as usual is threatening to kill Java
#7"It's a dangerous game they're playing," Not for Oracle it isn't.
I wouldn't invest (not even my time) in licenses and staff to work over a platform that won't be maintained in the next 5-10 years.
Stability is better for business.
Re: How Oracle’s business as usual is threatening to kill Java
#8I code all kinds of stuff in Java and never use Java EE; JDK8 SE is great and I like some what is planned for JDK 8, it always seemed to me that Java EE was a collection of second- or third- best technologies.
Re: How Oracle’s business as usual is threatening to kill Java
#9I code all kinds of stuff in Java and never use Java EE; JDK8 SE is great and I like some what is planned for JDK 8, it always seemed to me that Java EE was a collection of second- or third- best technologies.
That is what I was thinking. Java EE is was already losing mindshare to Spring.
However I still find this troubling for the future of Java. If they kill EE this casually, why wouldn't they slowly abandon Java altogether . Java EE is the canary in the coal mine.
Not that I would be sad about Java's demise. Many companies see Java as they only real programming language. Maybe if Oracle keeps it up the enterprise will start to consider using other languages.
Re: How Oracle’s business as usual is threatening to kill Java
#10How likely is it that Oracle could sue a company using Java? Are you safe as long as you don't create something Dalvik-like? I have a gut feeling that lawsuit has had a chilling effect on enterprise Java usage. It obviously didn't put Oracle in a good light.
No group I've talked with has any concern for being sued over implementing java applications. The actual concerns are mainly whether oracle will continue supporting the ecosystem - security and features.