3 ms·
Worth noting that if you can, don’t stay on LTS. It adds cost which many modern teams can avoid[1]. It doesn’t mean enabling Java 18 on Production on day 1, bu
by signal11 5y ago
Worth noting that if you can, don’t stay on LTS. It adds cost which many modern teams can avoid[1].
It doesn’t mean enabling Java 18 on Production on day 1, but certainly it means adding a Java 18 compiler to your CI, running tests using Java 18, etc.
[1] https://www.reddit.com/r/java/comments/o0m6g8/the_state_of_project_loom_with_ron_pressler/h1zxsom/?context=3 https://www.reddit.com/r/java/comments/o0m6g8/the_state_of_p...
- throw0101a 5y agoYes, newer JDKs should ideally be rolled into at least DEV and perhaps QA just so breakage can be found early and fixed early. STG/PRD of course is something else. Even if you don't use any of the new features, there may be deprecation warnings and such that one should be aware of sooner rather than later. Tweaking early to ensure compatibility with current-LTS and future-LTS versions is worth some cycles: if you don't, you'll pay for it eventually when old(er)-LTS is inevitably retired.
- danudey 5y agoThis discussion immediately brings to mind all of the iOS apps that become completely unusable the day a major iOS update is released, and then take a week to fix. I get that not everyone has spare time and energy, but it doesn't take that long to grab a beta, put it on a device (or load up the simulator) and find out. Leaving it until the last minute just forces you into a panic, and seems irresponsible when you had months to just test your product.