Reference URL: https://dzone.com/articles/5-myths-about-how-java-is-upgrading-to-become-bett
Five Myths About Java
Mark Reinhold addressed the top five misconceptions (otherwise known as fear, uncertainty, and doubt, or FUD) about the new Java release model:
- Feature releases will be disruptive for past releases - not true. Mark Reinhold said, "The rate of innovation has not changed, the rate of innovation distribution is changing."
- For removing an old feature, it must be deprecated three years in advance. “Not true, for removing a deprecated feature, it requires a production-ready build that issues a suitable warning at either compile-time or runtime because a working build, after all, is the ultimate release method.”
- Your support will end for any non-LTS release after six months and not more than three years for the LTS release. "That's not true; it depends on what the non-Oracle members of the JDK community decide to do. Oracle has a proven track record and is already discussing how best to support JDK 8 and JDK 11 for the long haul.”
- Non-long-term-support releases are just another name for a beta. “No, the only difference with an LTS release is that it has a longer support timeline,” Reinhold said, “You can still use a non-LTS release in production if you like, but you’ll have to update it in six months or find someone to support it or support it yourself.”
- If you maintain an infrequent migrated system, you can ignore non-LTS releases, " Reinhold claims this is also not true, claiming, "if you test with each feature release, then you are ready to migrate to the next long-term support release.”
What do you think about the new release cycle? Let us know in the comments below!