4 ms·

I'm in a 4th camp: we should be writing our applications against a relational data model and _not_ marshaling query results into and out of Objects at all. Ela

I'm in a 4th camp: we should be writing our applications against a relational data model and _not_ marshaling query results into and out of Objects at all. Elaborations on this approach: - https://news.ycombinator.com/item?id=34948816 https://news.ycombinator.com/item?id=34948816 - https://github.com/papers-we-love/papers-we-love/blob/main/design/out-of-the-tar-pit.pdf https://github.com/papers-we-love/papers-we-love/blob/main/d... - https://riffle.systems/essays/prelude/ https://riffle.systems/essays/prelude/

pjmlp 3y ago
Still on the 4th camp? Using stored procedures and triggers as much as possible.
specialist 3y ago
Nice share, thanks. I was never more productive than when using Access (and dBase II before that). Why can't we have that? My theory: Something was lost in the jump from workgroup computing to client/server. Imagine if Access was rebuilt on top of a client/server stack. That's kind of what Riffle is trying to do. I've been (slowly) working on the persistence stuff. It (mostly) moots the SQL vs ORM vs query builder slap-fight. I've got some notions (and POCs) about UI, mediated via HTTP & HTML. I'd love to have some CRDT-like smarts; learning more is on my TODO list. I'm still thinking about the "reactive" part. I haven't imagined anything past Access VBA style programming. I'm struggling to envision a FRP-meets-CRUD future perfect world.
- tantaman 3y ago
  > I was never more productive than when using Access (and dBase II before that). I've never used access and have 0 familiarity with it. Are there any examples I could look at?