3 ms·
This seems like an excessively uncharitable read of the situation. I've never used Nubank's software, but I have used (on-prem) Datomic and I certainly wouldn't
by tomconnors 6y ago
This seems like an excessively uncharitable read of the situation. I've never used Nubank's software, but I have used (on-prem) Datomic and I certainly wouldn't say it has bugs everywhere. In fact, in my (admittedly low-volume and simple) usage of the system I haven't come across any bugs I can remember. Calling Cognitect a "burnout" company is inaccurate and rude.
I agree with you that the Datomic cloud stuff comes across as being frighteningly complex. I think they probably just need to work on the documentation, like making it more obvious what the differences and tradeoffs are between the deployment scenarios.
Did you inherit a Datomic system that was previously developed by a small team or a small company? Because inheriting a system that's hard to understand and change transcends languages and databases. It is the tie that binds us all as software developers.
- Scarbutt 6y agoI hit this bug: https://docs.datomic.com/on-prem/changes.html#0.9.6021 https://docs.datomic.com/on-prem/changes.html#0.9.6021 Not being able to perform writes to your database is not scary enough? it's funny how they phrased that bug. Also hit 4-5 more that are there in the change log, let serious but still pretty bad and frustrating. This was a internal application, the DB was not being stressed, a 4KLoC readable Clojure codebase. Don't get me wrong I really like Datomic and its features but the implementation still has a long way to go.
- tomconnors 6y agoFair enough, hitting that bug would have pissed me off too. On your last point, I agree that it still has a way to go. It's good for some (many?) production use cases now, as Nubank's success demonstrates, and hopefully with Nubank's resources it'll start to live up more to its promise.