There are an order of magnitude more application developers today than just 10 years ago. This enable us to invest much more in the tools we all use, resulting in higher quality and a much better experience.
So to turn it around - why _not_ build new and better tools?
Is that supposed to be a reason against? Enabling further progress sounds more like a reason for, not a reason against.
With Prisma, we're setting out to build database tools that make developers more _confident_ and _productive_ [1] in their database workflows!
We're focusing on type-safety, intuitive data modeling, easy working with relations and overall simpler ways for achieving common tasks with your database.
We also wrote at length about what we believe the shortcomings are with databases tools in our documentation [2], would love to hear your feedback about our thoughts here!
[1] https://www.prisma.io/blog/announcing-prisma-2-n0v98rzc8br1/
Even after reading your (three) paragraphs from the article on why raw SQL and drivers are bad, I'm far from sold.
1. Establish connection 2. Execute SQL 3. Manipulate results 4. More SQL/Commit/close
IME a lot of the struggle comes from not understanding how 1. or 2. work and trying to do all the heavy lifting in 3. The amount of times I've refactored dozens of lines of code into <10, with huge performance and readability gains by simply using SQL's potential...
Best of luck with the sales.
There is absolutely room for improved tooling. I have no idea whether Prisma is it.