You also can’t really hire Datomic people in bulk so that knocks out anyone trying to scale their eng org.
I can see it working well for companies who are trying to do a lot with a small very bright staff, but that’s a small category. And even then it would only be places where the staff has consensus around immutability as a value.
Which... immutability, like many forms of strictness, is both a PITA and not actually that helpful unless you go all in.
It’s just a major commitment and for what benefit?
Maybe for a product where you need rewind everywhere.
Maybe for a product where you need extreme auditability.
I don’t know... what’s the killer feature that would make someone sacrifice everything else to use it?
Personally I think Datomic needs to be paired with a hosting system, debugging tools, basically some kind of integrated development environment that’s immutable-first in every respect.
Something like that would be powerfully differentiated.
I think the benefits have been pretty well laid out and are quite attractive, your restatement of them is just damnation with faint praise :)
> Maybe for a product where you need extreme auditability.
These are "nice to have"s or "wish I had it but it's too late now"s for a lot of products though
Maybe in a v0 release, most applications can get away with created & modified fields. Maybe the storage overhead of immutability scares people for some applications.
Maybe datomic is something that should be part of a powerful DB plugins ecosystem rather than its own database, or as an external audit log that can be written separately while keeping your main DB in SQL.