[dewey]

There's a general pattern of:

    - People inventing new technologies to not write SQL   
    - People inventing ways to avoid writing HTML

I feel like the solution to both of these is just to stick to SQL / HTML as for both of these there's a lot of resources, tooling and knowledge and they will not go away. They are transferable between languages, projects and whatever tooling companies are using.

[MyOutfitIsVague]

HTML, yes, but SQL has another major problem in that it's not composable. HTML can be broken into fragments, but it's very difficult to work with and write reusable SQL in a modular way. CTEs and views help a bit, but they are not a great answer to the fact that SQL statements almost always have to be treated as an indivisible chunk.

I like SQL alright from a functionality perspective (the syntax leaves much to be desired), but I still use ORMs where appropriate just to be able to modularize and make reusable behavior where it makes sense.

[dajonker]

It's a necessary evil, isn't it? You're not programming your application in pure HTML or SQL, you write it in some general language that can do much more. But the browser and database don't speak that language natively. They want strings which they then turn into something useful. So you need to build these big strings and unless your application is completely static, you'll need string interpolation one way or another.

[3by7]

And

  - People inventing new technologies to not write JS
  - People inventing new technologies to avoid writing CSS

[joeldrapper]

How do you write an each loop or a conditional in HTML?