Persistent Collection VS Persism

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.

> 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.

You might consider persistent collections instead of immutable collections, I believe it is more optimized https://github.com/hrldcpr/pcollections

People would be much better off using Persism https://github.com/sproket/Persism

Yes, you do also have to add the mysql-connector-java-(version).jar to the classpath. If you run it in eclipse, it should show the command line it uses somewhere. BTW if you're looking for a simple streamlined ORM have a look at persism

If you use Java you might like Persism https://github.com/sproket/Persism if you need to do anything databases.

If you want to try a easy to use ORM have a look at Persism

It's not that good. It doesn't have persism on it yet https://github.com/sproket/Persism

Is there a reason it needs a dependency on Lombok? If you want a library to be used, the less dependencies the better. See mine. It has zero.