docs: Rework list of JEPs and mention more projects

Author: tgodzik

_posts/2025-02-01-next-scala-lts.md

@@ -43,9 +43,12 @@ Some of the features that might be interesting to the Scala community are:
   distinct class files, to access each other's private members without the need
   for Scala compiler to insert accessibility-broadening bridge methods. This is
   especially useful for nested classes or companions.
-- [JEP 334](https://github.com/scala/scala3/issues/22294) introduce an API to
-  model nominal descriptions of key class-file and run-time artifacts, which can
-  potentially help improve the internals of Scala 3 compiler.
+- [JEP 409](https://github.com/scala/scala3/issues/22298) which introduces
+  sealed classes and would allow the compiler to better represent the Scala's
+  sealed trait hierarchy.
+- [JEP 441](https://github.com/scala/scala3/issues/22450) would similarily allow
+  us to optimize code resulting from pattern matches using the introduced
+  pattern matching for switch statements in Java.
 - [JEP 471](https://github.com/scala/scala3/issues/9013) which adds a new API
   for memory access, which can be used to replace the usage of sun.misc.Unsafe
   in Scala 3.
@@ -63,9 +66,27 @@ already stopping or will soon stop updating JDK 8 with security and other fixes,
 which might directly impact issues within your business applications.
 
 Some larger projects within JVM and Scala ecosystems have already dropped JDK 8
-support. And while it's always possible to not update your libraries and Scala
-version, which will avoid having to switch to a newer JDK, it's highly
-discouraged as it will make you vulnerable to potential security risks.
+support or even went straight to 17, these include:
+
+- [Spark 4](https://github.com/apache/spark/pull/43005#issuecomment-1731344040)
+  will require JDK 17
+- [Play Framework](https://github.com/playframework/playframework/issues/11078)
+  already dropped JDK 8 and will stop supporting JDK 11 in the next major
+  release
+- [Akka](https://github.com/akka/akka/pull/32127) dropped JDK 8
+- [Spring 6](https://spring.io/blog/2022/11/16/spring-framework-6-0-goes-ga)
+  will support JDK 17 and up
+- [Logback](https://logback.qos.ch/dependencies.html) requires JDK 11
+- [Apache Kafka](https://kafka.apache.org/documentation/#java) deprecated JDK 8
+- [Hibernate](https://hibernate.org/orm/releases/6.6/) requires JDK 11 and the
+  next version will go to JDK 17
+- [ZIO](https://github.com/zio/zio/pull/8434) dropped support for JDK 8
+- [Li Haoyi's ecosystem](https://github.com/com-lihaoyi) dropped JDK 8 across
+  the board
+
+While it's always possible to not update your libraries and Scala version, which
+will avoid having to switch to a newer JDK, it's highly discouraged as it will
+make you vulnerable to potential security risks.
 
 ## Plan for making the switch