Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider migrating away from guava library (or make its use internal) #607

Closed
laeubi opened this issue Nov 5, 2023 · 3 comments
Closed

Comments

@laeubi
Copy link

laeubi commented Nov 5, 2023

Google Guava is a collection of useful things but there also lies its weakness as this results in big size, and heavy dependencies on specific versions even if not all parts are affected. Also with today modern java many things can be archived with plain java as well.

As it is know to create dependency-hell problems, I'd like to suggest to:

  1. replace all usages where possible with standard java
  2. embeds the code that can't be replaced easily in an internal package

See

for a discussion where the usage of guava currently prevents usage of LSP4J in eclipse-platform while it seems a technology that should be used even more there and currently requires several plugins to ship their own what can then create even more problems of competing versions.

See also

@sebthom
Copy link
Member

sebthom commented Nov 7, 2023

Done

@sebthom sebthom closed this as completed Nov 7, 2023
@laeubi
Copy link
Author

laeubi commented Nov 8, 2023

@sebthom wow that's great news!

@vogella
Copy link
Contributor

vogella commented Nov 8, 2023

@sebthom super impressive. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants