Customers don’t want to learn your schema or deal with your clever optimizations either. If you expose a DB make sure you abstract everything away in a view and treat it like a versioned API.
The best example for this are iot devices that share their data. Instead of reinventing the wheel for a dashboard for each customer just give them some docs and restricted access via a replica.
While no doubt all these changes are for the best I have to wonder how many are using htmx for the same reasons as I do. It’s simple. I don’t need much functionality. I don’t want to spend time in frontend work so any changes are just a pain and only risk losing business. Htmx 1 and Django are working great for me and I don’t need to change for some time.
I think they are a decade or two late to migrate away. They will end up developing their own in a time where these are loss leaders. It’s likely they will pay for it in a bundle while just not using it.
Not to mention in my experience EU companies don’t know how to migrate away from anything as their tech companies operate at the efficiency of a US government agency.
reply