8/25/2023 0 Comments Java 11 openjdkThese are, however, production-ready releases. Every 6 months a new Java version is released, the so-called non-LTS releases Java 12 up to and including Java 16. Also, with Java 11, the Oracle JDK was not free anymore for production and commercial use. Java 11 came with support up to September 2023 and with an extended support up to September 2026. With Java 11 a new release cadence started. Java 17 is an LTS (Long Term Support) version just like Java 11. Introductionįirst, let’s take a close look at the Java licensing and support model. A short introduction is given about the licensing model and after that, some of the changes between Java 11 and Java 17 are highlighted, mainly by means of examples. Time to take a closer look at the changes since the last LTS release, which is Java 11. Adobe can eat a bag of dicks too I hate their bloated software.The 14th of September Java 17 was released. My response was that the users in my company that are using adobe creative suite are using licensed versions that were downloaded from their portal that are tied to their adobe user accounts, and that they only have the software installed on one machine per user. When I graciously declined, I got a nastygram back telling that it is a licensing audit and that it is mandatory. I had a similar exchange with Adobe in regard to licensing, which was sent under the guise of reviewing our current products to see if there was a better solution for us. Oracle can pound sand, we're not bound by their current licensing and we are compliant for the version of the license that the versions we do still use on older systems were licensed under. They were sending us emails once every couple of days, so I created a proofpoint mail filter to block emails from Oracle. We sat down with our developer and all systems we use either have an older version of Java that predates any of the newer more restrictive licensing, or OpenJDK. Note that the word were is stressed for this statement. We "WERE" getting compliance emails from oracle wanting to talk about license changes they were still running the old product too. Heck, I once worked at a company where their new product (to replace their old crusty product) was 15 years old. I've seen the 'rip it out because some suit has a panic' approach in the past, it often doesn't work well. It could be done piecemeal as components came up for change. Se we got all the syntactic sugar benefits and the resultant improvement in development time but we didn't have to re-factor a large portion of the codebase. It meant programmers could develop in a nicer language, but the existing codebase wasn't invalidated as the two interoperated well. Often these kind of projects can spiral, and if you're not doing them for good reasons in the first place you're just pissing away good money after bad.įor example, I worked at a Java place that disliked the way Java was head, so they moved to Groovy (A sadly overlooked replacement). If it's personal dislike, then make sure you're also doing it for good technical/business reasons too. At least have a road map leading to eventual cleanliness.Īlso, ask yourself 'why' too. (IMHO), but the VM and runtime are okay.ĭisinfecting everything of dirty contaminated toxic crap is never a bad idea. In fact, if you dislike Oracle surely using their work without payment is the ultimate 'fuck you'? (I'll be fair to them, they aren't that bad at databases).Īnd getting rid of Java is a good idea even if it wasn’t Oracle. Maria uses innodb or ISAM which is still Oracle.Īnd GPL2 licenced, so not a problem. Even if that's executives misunderstanding and just decreeing "No, no more Java, or anything associated with it, I don't want to see another threatening Oracle bill!", that's no bad thing from the business's point of view. Java is being tainted by Oracle, and people are beginning to want nothing to do with it. I'm watching vendors who are dependent on supplying Java software (including some embedded in hardware) scramble to move us to their new versions that aren't. Why would you want to be dealing with Java clients nowadays? even more of a case to just move in the modern age. If the time was already ripe to consider moving, and you start getting this hassle, and you feel there's no future in Java - that's the time to just burn the bridges and start afresh on something without any such licensing whatsoever.Īnd if you have no Java on servers. I don't think it's stupid - I think that's a sensible business decision, because Java is about to start going the way of the dodo because of actions like this, and who wants to deal with any fallout from - say - an Oracle/OpenJDK lawsuit, hassle from Oracle over your exact usage, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |