4 ms·
Thank you for your feedback. I'm using Guava because of its immutable collections. There are alternatives, so changing this is probably not that hard. However,
by moring 3y ago
Thank you for your feedback.
I'm using Guava because of its immutable collections. There are alternatives, so changing this is probably not that hard. However, it would help to know what exactly you don't like about Guava, to avoid replacing one problem with another problem.
- vips7L 3y agoWhy not just use the modern List.of, Set.of, Map.of immutable apis from the standard library?
- moring 3y agoI didn't know this was a thing... what a major oversight! Now one big reason for Guava has just disappeared. Thanks a lot!
- flashharry 3y agoI'm just a bit allergic to unnecessary dependencies and Guava is a massive blob of a jar. It's not properly modularised so you can't just pick the bits you need, if you want to use a single feature from it you have to include all of them. This can cause problems if someone who wants to use your framework also wants to use a different version of guava. In general the fewer dependencies your framework has the easier it is for people to use it.