Re:Exodus: Easily migrate your JVM code from Maven to Bazel
by erik_seaberg on Wednesday April 07, 2021 @02:19AM
(#26721112)
It came from Googlers, who are kind of notorious for not using the rest of the industry’s tools. Sometimes it’s because they pioneered the problem space, and their own tools really are that much better. Sometimes their tools used to be better but are now just tech debt. Sometimes it’s promo-driven development.
Re:Exodus: Easily migrate your JVM code from Maven to Bazel
by vips7L on Wednesday April 07, 2021 @07:42AM
(#26723396)
> Sometimes their tools used to be better but are now just tech debt
This is how I feel about most of Googles Java libs (guice, guava, gson). They used to be better, but now they're just tech debt.
Re:Exodus: Easily migrate your JVM code from Maven to Bazel
by alexhutcheson on Wednesday April 07, 2021 @01:21PM
(#26727873)
What are the best-in-class replacements for those?
Re:Exodus: Easily migrate your JVM code from Maven to Bazel
by vips7L on Wednesday April 07, 2021 @01:43PM
(#26728212)
Guava -> The JDK Std library, unless you need more performant collections provided by it.
Guice -> If you need to support the jakarta.* namespace the only real answer is Weld or another CDI compliant implementation. Otherwise guice is probably still fine.
GSON -> Jackson as always.
The Java ecosystem has much of that available also though - even a large Java-only project is somewhat tough to justify moving away from the tools almost every developer will arrive already knowing.