Persistent Collection
record-builder
Our great sponsors
| Persistent Collection | record-builder | |
|---|---|---|
| 4 | 35 | |
| 746 | 647 | |
| - | - | |
| 6.6 | 7.2 | |
| about 1 month ago | 14 days ago | |
| Java | Java | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Persistent Collection
-
I had a great experience with Scala and hopefully it will get more popular
So does Java! Also, kotlinx.collections is still not stable and I don't think they are intending to make it so any time soon.
-
What’s so great about functional programming anyway?
> If you are using containers, always, always, always use immutable containers from Google Guava unless you have an exceptionally good reason.
I actually prefer pcollections: https://github.com/hrldcpr/pcollections
AtomicReference + immutable data types is a really nice way to program in Java, and is basically the way most Clojure programs are written.
- Why Java's Records Are Better* Than Lombok's Data and Kotlin's Data Classes
-
Libraries, Frameworks and Technologies you would NOT recommend
You might consider persistent collections instead of immutable collections, I believe it is more optimized https://github.com/hrldcpr/pcollections
record-builder
-
JEP Draft – Derived Record Creation (Preview) – Java
The problem with this approach is that the people will have to build crutches like https://github.com/Randgalt/record-builder and by the time Java adds missing features all the codebases will be forever polluted with legacy workarounds that nobody will dare to remove because of backwards compatibility.
It also hinders adoption of new features as people will prefer to maintain consistency in their codebases.
-
Any library you would like to recommend to others as it helps you a lot? For me, mapstruct is one of them. Hopefully I would hear some other nice libraries I never try.
Record builder is pretty good for making builders for your Java 17 records
-
Useful & Unknown Java Libraries - Piotr's TechBlog
I always have to bring up RecordBuilder simply because of the included Withers and it being a source generator instead of the Lombok weirdness.
-
How to use Java Records
The above is not particularly user-friendly. Luckily compiler plugins can provide the missing feature, most notably RecordBuilder:
-
Named Parameters in Java
For records, instead of lombok you can use https://github.com/Randgalt/record-builder which is a valid annotation processor and will not break on JDK changes
-
has anyone written custom annotations using Lombok ?
In this particular case you can generate the builder with something like https://github.com/Randgalt/record-builder that is both valid java and lombok-like enough
-
I made a java client for the todoist api
Records + Record Builder or immutables + the trick to hide the implementing class w/sealed are your friend. Both the mutability and naming conventions this generates are vomitus.
-
"With" for records -- Brian Goetz
Did you use https://github.com/Randgalt/record-builder ?
-
What's your top Java pet peeve?
Try my annotation processor. It generates withers. https://github.com/Randgalt/record-builder
-
Stay with Java(+Spring) or pivot towards Go/Python?
I personally don't use that one much, but you could use this library instead.
What are some alternatives?
Big Queue - A big, fast and persistent queue based on memory mapped file.
MapStruct - An annotation processor for generating type-safe bean mappers
tape - A lightning fast, transactional, file-based FIFO for Android and Java.
Lombok - Very spicy additions to the Java programming language.
Apache Parquet - Apache Parquet
awesome-annotation-processing - A curated list of resources related to the Java annotation processing API (JSR 269)
SBE - Simple Binary Encoding (SBE) - High Performance Message Codec
core - An advanced and highly optimized Java library to build frameworks: it's useful for scanning class paths, generating classes at runtime, facilitating the use of reflection, scanning the filesystem, executing stringified source code and much more...
Protobuf - Protocol Buffers - Google's data interchange format
Immutables - Annotation processor to create immutable objects and builders. Feels like Guava's immutable collections but for regular value objects. JSON, Jackson, Gson, JAX-RS integrations included
dexx - Persistent (immutable) collections for Java and Kotlin
Jackson JSON Processor - Main Portal page for the Jackson project