Comments by "Brent Jacobs" (@br3nto) on "The Stockholm Syndrome of SQL | Prime Reacts" video.

8:54 there are sooo many improvements that can be made to SQL even without inventing something by totally new. First, put FROM statements first. How can you get code completion in your SELECT clauses without knowing which tables the data will come from? Second, name table relationships. Instead of joining, you use the relationship name. There are so many query patterns that could be abstracted, though I guess that’s what stored procedures are for. The other thing that gets me is that all RDBMs are also inherently object/graph databases. So in theory, they could all have object/qraph QL applied. The other other thing, is that SQL or an improved derivative language could be used by clients instead of GraphQL to query APIs. The whole data persistence part could be abstracted so that you get secure decoupling between the domain data and the persisted data.
4
4:48 is Deno ugly too?
1
18:59 SQL isn’t just a string literal. It’s really no different in concept from sending shaders to a GPU or sending bytecode to a JVM, or instructions to a CPU, or a request to an API.
1
@isodoubIet sure, but that’s a different issue to the string literal comment.
1
@isodoubIet how?
1
@isodoubIet how is it “exactly the issue”?
1
@isodoubIet it’s not just a string though. You can’t just write anything. It’s a declarative language that is literally interacting with the API of the database schema and/or database engine. It’s pretty much the same as calling an HTTP server, or Redis, or a GPU, or a CPU, or sockets, they are all one thing getting another thing to do something using 1s and 0s.
1