Ten reasons to use Eclipse Collections

You may only need one.

It’s a sign

Top Ten Reasons to use Eclipse collections

1. Rich, fluent, and functional API with good symmetry (productivity)
2. Memory Efficiency (performance)
3. Optimized Eager API (performance)
4. Primitive Collections (productivity & performance)
5. Immutable Collections (safety & performance)
6. Lazy and Parallel Lazy API (performance)
7. Multimap, Bag, BiMap, Pool, Interval (productivity & type safety)
8. Hashing Strategy Data Structures (productivity & performance)
9. Multi-reader data structures (safety and performance)
10. Mutable and Immutable Collection Factories (productivity)

If the collection framework(s) you are using today is (are) missing one or more of these features, and you need them, then it would really be worth your time to check out and try Eclipse Collections.

Additional Reasons to try Eclipse Collections

1. It’s open source and managed at the Eclipse Foundation and you can contribute to the library if there is something you need
2. Eclipse Collections 9.0, 9.1, 9.2, 10.0, 10.1, 10.2, 10.3, 11.0, and 11.1 were released with a lot useful features that were contributed by many members of the open source community
3. There are fun code katas to get you started
4. Easy to understand and refactor to if you already know lambdas/ streams
5. The Eclipse Collections website is available in eleven different languages

I am a Project Lead and Committer for the Eclipse Collections OSS project at the Eclipse Foundation. Eclipse Collections is open for contributions. If you like the library, you can let us know by starring it on GitHub.