"Unparalleled productivity" sounds like hyperbole, especially considering the posts below, showing how exactly the same thing can be done trivially in Postgres.

Do you have an example?

It's because Datomic doesn't have the object/relational impedance mismatch. Because immutbility yields idealized caching so a lot of hard performance problems inherent to RDBMS go away. It's like moving from CVS to Git.

Fuck it, hyperfiddle isn't launched but lets just post it here. Hyperfiddle is JSFiddle + Datomic. http://hyperfiddle.net/ If you care about this, you should reach out, please email me!

It sounds like the site's not finished yet, but FYI it's a trainwreck on iPhone6 + Safari

I like the idea. Nice work!

This doesn't answer your question, but I just wanted to make clear that the posts below certainly do not show, trivially or otherwise, how to use "no string literals" and "pure data" in Postgres.

Those concepts don't make any sense, so it's no wonder that a serious RDMBS like Postgres doesn't support them.

Can you explain your statement?

Can you explain what those concepts mean and why are they important? It's the first time I've read about them or Datomic for that matter.

I asked since I don't know much about datomic either or how usable is it in production. So I haven't much to share.

> especially considering the posts below, showing how exactly the same thing can be done trivially in Postgres.

So then where is the open source version / extension to Postgres?

How about this - I'll give you $1000 if you can give me a seamless extension on top of Postgres that has most of the functionality of Datomic.

Since it is trivial it is easy money for you.

GGP talked about building a CRUD app with "unparalleled productivity". That's where the burden of proof is, not to the GP who is skeptical about that claim.

"So then where is the open source version / extension to Postgres?"

As a concrete example I like the way in the datomic schema you can eliminate bridge tables for many-many relationships using :db/cardinality :db.cardinality/many and then you store or get a vector.

There should be a way to have a super-SQL middleware compatible with any language bindings including a bare CLI that eats "SQL plus some cardinality" and behind the scenes implements the bridge table manipulations. Don't repeat yourself and all that, and many/many tables are kinda repetitive.

There doesn't seem to be anything remotely like that out there.

You are asking for evidence of disproof. That is a logical paradox, and frequently used as an argument by extremist politicians.

Where is the evidence that you do not [insert anything here]? That's a slippery slope of challenge.

yep https://stackoverflow.com/questions/42457136/recursive-datal...

https://groups.google.com/forum/#!topic/datomic/insqPDtbvjk

Unparalleled productivity maybe, but only once you've learned how to read code that looks like an AST, and to juggle parens in Emacs (learn paredit etc).

For better or worse, history has proven that doesn't appeal to many developers. Lisps just aren't popular, and that lack of mindshare matters.

There is parinfer which turns lisp into a white space significant language, no special commands necessary