Oracle to charge for Java from Jan 2019(itassetmanagement.net) |
Oracle to charge for Java from Jan 2019(itassetmanagement.net) |
This is blogspam and FUD. Java SE 8 will be past EOL at that point. Oracle has announced no intent to charge for updates to Java SE 11, which should be the current release, at that point.
Java 9 is out. Java 10 is out. I can see why oracle might want to cut down their support costs and retire their older versions more quickly.
However this will blow up in their faces if a lot of software gets exploited due to unpatched vulnerabilities.
I’m no fan of Oracle of their sales practices but the title is very misleading by omission
JDK (and JRE) 11 will be the latest version by then. Only companies which need or want to stay on the previous version will have to pay.
1. It's about EOL SE 8
2. "software running Java SE 8" - the article needs to be clear about Oracle Java, and Open JDK and others like Azul
As a result the headline and article come across as a bit FUDdy to me.
Microsoft's reputation isn't what Sun's was, but it's miles better than it was under Ballmer and light-years ahead of Oracle's. Looks like the bulk of .NET code is released under permissive licenses, too (?)
I don't know how much "hacker goodwill" buys you when you make old-people tech, but Java has definitely lost ground to its main competitor. Maybe their recent uptick in language development velocity will help things.
Sun spent like millions of dollars on Java, without earning a penny in return. At some point in time you are a company and have to make profits.
Sending all that big money down the drain for others benefits, and no profits for yourself is something no company will do.
Its not as simple as just recompiling code. Something like the entire ecosystem has to move, you will have plenty of compatibility problems, code breakage and catch-22 situations.
This is not good news for Java.
Also a lot of 'Architects' will be forced to think if they will be made to pay for Java later. Hence should they use something else to build their latest projects?
The EOL for JDK 8 has been known for quite some time now.
Architects who haven’t taken that into account yet have been negligent regardless of Oracle charging for future updates or not.
Migrations almost always require quite some effort but there was plenty of time to prepare in this case.
Either way, if it comes to a point where you have to pay for something like using a programming language. Pay whatever you have to now. But start moving to something other tech over time.
And yeah, don't start new projects in Java.
You can even continue using JDK 8 for free indefinitely. Just don’t expect any future updates from Oracle, security or otherwise.
If you absolutely have to use JDK 8 another option is OpenJDK, which unlike Oracle’s JDK probably will continue receiving updates even for version 8.
I also don’t see why one shouldn’t use Java for new projects. With its huge ecosystem and modern toolsets such as Spring Boot Java is a highly viable option for developing new applications.
At that point, you are just better off using something else to insulate you from things like these.
>>Just don’t expect any future updates from Oracle, security or otherwise.
That's a very big problem for most shops.
>>With its huge ecosystem and modern toolsets such as Spring Boot Java is a highly viable option for developing new applications.
Spring Boot isn't a configuration less framework. Its basically a only one configuration works framework, change something small and nothing works. Also code comes out so unmaintainable no one apart from the original authors generally understands anything about it.