Hacker News new | ask | show | jobs
by dustingetz 3207 days ago
JOIN tables, sparse tables, deeply nested JOINs - all this is needed to code link-following in the relational model. So you need an ORM to handle the JOIN pain for you, but relational db query perf degrades as your joins get deeper, so the ORM needs to make hard choices around caching and database query round tips - but the ORM doesn't have enough information about the UI to make these choices - you end up needing to code the app logic into the ORM via caching and query optimizations. And now you're writing code, that's not links and forms anymore.

At ClojureNYC last night I gave a talk about literally this! Here are the slides: https://github.com/hyperfiddle/hypercrud.browser/issues/4
1 comments
Norther 3206 days ago
Dustin, wow. I can see a lot of work went into your talk. I read along for about 80% and you make some great points. Hyperfiddle looks impressive - I signed up to the dev mailing list.

As an aside, do you think traditionally built apps should be moving away from SQL and towards immutable stores like Datomic?

link
dustingetz 3206 days ago
yes! Data driven UI (which is what this thread is about) will never succeed on sql.
link