Skip to content

Commit f05d62d

Browse files
SethTisueGedochao
andauthored
Update _posts/2025-03-05-next-scala-lts-jdk.md.md
Co-authored-by: Piotr Chabelski <ged.subfan@gmail.com>
1 parent 9970fb9 commit f05d62d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2025-03-05-next-scala-lts-jdk.md.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ decision to switch to JDK 17 as the new minimum, starting with Scala 3.8 minor
1111
and the subsequent new LTS which will mostly likely be Scala 3.9.
1212

1313
The discussion didn't uncover any compelling reason not to leave JDK 11 behind.
14-
11 is now nearly as antiquated as 8, and moving from 11 to 17 is not normally a
14+
11 is now nearly as antiquated as 8, and moving from 11 to 17 is not normally considered a
1515
difficult upgrade for users. 17 offers useful APIs and VM features. In the JVM
1616
world, requiring 17+ is already a mainstream position and is becoming more so
1717
with every passing month. Also, we increase Scala's minimum so rarely, we feel

0 commit comments

Comments
 (0)