Well, I've watched most of the video.
IMHO it's a step back.
You know separation of concerns, clean templates, don't mix presentation and data.
Well, this is the extreme in the opposite direction.
Instead of using proper <component>s you're using
"select 'Label' as text".
No. Even if the guy is sympathetic, keep presentation separate.
If it had markup mixed with SQL queries, ok, sure.
But this is going too much in the other extreme direction.
I not just would like but need to have control over my presentation.
And with doing pseudo SQL queries this is too complicated vs regular markup or something like vue etc.
Only upside of this is performance and/because it's SSR
It is indeed the complete opposite to "separation of concerns". But it's not necessarily a bad thing.
Why is separation of concerns a good thing in general? Mainly because of three things: maintainability, scalability, and collaboration.
However, there are cases where strict separation of concerns is impractical, and people are ready to sacrifice these for simplicity and speed of execution.
Agreed- I worked at a company a few years back that build on a product using postgrest and an angular frontend for everything with nothing in between- which felt wrong as well
Instead of using proper <component>s you're using "select 'Label' as text".
No. Even if the guy is sympathetic, keep presentation separate. If it had markup mixed with SQL queries, ok, sure.
But this is going too much in the other extreme direction.
I not just would like but need to have control over my presentation. And with doing pseudo SQL queries this is too complicated vs regular markup or something like vue etc.
Only upside of this is performance and/because it's SSR