It's been already 4 months since JDK17 was released, but Guice (one of the most popular Java dependency injection frameworks) still didn't release required compatibility changes [1]. There looks to be zero contact with maintainers at Google. In the meantime Spring was ready for JDK17 in July (3 months before JDK17 GA) [2]
For years I advocated to use Guice at my companies, as it's considerably less bloated than Spring. Now I'm starting to get some heat on this as it's clear that the support is just not there. Is this the right time to accept the defeat and start migrating back to Spring?
[1] https://github.com/google/guice/issues/1536 [2] https://twitter.com/snicoll/status/1420652097373188100
However, Google only upgraded to JDK11 in 2021, so there's probably not much internal pressure yet to keep Guice up to date with JDK17.
If you're concerned about bloat you could look into Quarkus. There's a CDI implementation there combined with a really slick and fast runtime.
[1] https://github.com/google/dagger
Creating fork that I don't have time nor skills to reasonably maintain sounds like a recipe for even more problems.