From an efficiency standpoint it would be way better when devs run this once and not every visitor.
[1] https://docs.oracle.com/en/database/oracle/oracle-database/2... [2] https://blogs.oracle.com/developers/post/creating-a-graphql-...
I also like Svelte which uses it's own language and needs transpilation. I think that's key to elegance as JS was not really designed to control layout, style and logic all at once.
They do a good job about it and want to share it so they publish their story. Now people from other companies read this and think that this is now state of the art and they also should do this. But they don't even have the same issues.
I work with a Low Code framework from Oracle (APEX) that literally runs in the database and serves web apps. Want a report and form on a table? Click create new app and xreate page, select the table, customize labels, maybe move things around, maybe change an item from type text field to select list with another query and done in 5 minutes. With lost update detection, easy authorization control, automatic validations for your table constraints, etc. You can still code data processing procedures but why reinvent the wheel for another web UI?
People just choose to overengineer backend apps that only 50 people use...
I have a friend who works in such place. DeepL is a most important piece of software he uses, the problem starts if DeepL messes up some details. Meetings are a nightmare, communication is a nightmare. Managers try to mitigate all that, by avoiding employees from Germany in the projects, what is pretty funny, as company is multinational, but of German origin, and most of the managers are Germans...
This attitude is just one of the many factors that led to https://www.amazon.pl/Kaput-German-Miracle-Wolfgang-Munchau/...
More about my experience on my blog: https://hartenfeller.dev/blog/testing-claude-code