Ask HN: Google Guice another abandonware from Google?
11 comments
I work on the team that maintains Guice and we are working on a new release. And no, Guice is not abandonware since it is widely used inside Google. As part of this new release, we will be making some changes to the build setup so hopeful future releases will occur more frequently.
Guice is pretty old now, like 12 years or so. That's a pretty good run for a programming library, and wouldn't put that in the same class of abandonment as other Google shutdowns.
It's still great library, doesn't miss any features. I just wish it was still maintained, as for some apps I own its almost impossible to migrate.
Guice forms a core part of many of Google's internal Java frameworks, so it's unlikely to be deprecated anytime soon.
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.
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.
Yes, I don't know anyone who uses Guice, but lots of people who use Spring. The momentum was never there, nor it will be.
If you're just concerned about dependency injection there's also the CDI standard way of doing things where there are multiple implementations to choose from.
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.
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.
Hasn't Google Guice been superseded by Google Dagger? [1] As far as I know Guice seemed to be in maintenance mode for quite a while now.
[1] https://github.com/google/dagger
[1] https://github.com/google/dagger
As far as I understand, Dagger is doing more stuff on compile time and was meant for resource constrained environments like Android. There is no feature parity between the two.
Just fork it. But JDK17 support was fixed Sep 2021
It was fixed, but the new version was not released. I guess if you work at Google everything works for you.
Creating fork that I don't have time nor skills to reasonably maintain sounds like a recipe for even more problems.
Creating fork that I don't have time nor skills to reasonably maintain sounds like a recipe for even more problems.
I'm using com.google.inject:guice:5.0.1 from February 2021 with no issues on JDK17...? Can't remember if it's significant but I'm also using org.ow2.asm:asm:9.1
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