This talk didn't hook me, but then again, it looks like it's aimed at developers who jumped on the NoSQL bandwagon and now need to be told why SQL is clever. I

This talk didn't hook me, but then again, it looks like it's aimed at developers who jumped on the NoSQL bandwagon and now need to be told why SQL is clever. I feel that much of what we do with map, reduce, sort and filter on arrays in modern JS is similar to SQL. Unfortunately, there is no query optimisation, because that would break your procedural code. What I'd like to see more of is domain-specific languages embedded in general-purpose languages, like React with JSX, or just a better bridge between the two. We have these two worlds of in-memory data structures on one side, and databases on the other, that we keep separate. NoSQL was an attempt at bringing them together, but it put far too little emphasis on complex queries and filters. It would be nice if we could just define data structures and their relations once and not have to do it again. It would be nice if foreign keys neatly mapped to object references in OOP and everything stayed live, so if you change a reference, that happens instantly in the database too, unless you wrap it in a transaction block. Now pull this off while still retaining the ability to open an SQL REPL to test out statements, or manipulate field definitions. I think that's what everyone wants, really. A seamless way for code to interact with data on all levels, with no perceptible boundary once you've opened a session to your DB server.