I believe the principles the article author is looking for are core to Pivotal Tracker.
I've often tried to persuade teams to use Tracker, but everyone sure loves the whiteboard metaphor!
For anyone wanting a actual full-stack framework with sensible defaults, type checked sql+api+rsx, and overwhelming community approval, don't reinvent the wheel: It has existed for years and is called https://leptos.dev
(If you're just making a simple rest api backend, I still dig the simplicity of poem-openapi + sqlx)
I can't understand if rust on rails is a joke, badly written by gpt, or written by someone who doesn't understand both Rust and web development in general. It's full of typos and baffling design decisions. (shelling out to an external comand to generate rust code?! MACROS EXIST!)
This is the right answer.
How can you go back to a non-typed world after Rust I don't know.
I use html-node which has a typed submodule for even greater strictness.
I just build some valid html, make a string and write that to the output directory and get on with my life. Eg:
https://github.com/0atman/noboilerplate/
Templates... Rust functions
Flow control... Rust match expression
Abstraction... Rust modules
Html validation... Rust compiler
I like to think that in writing the html-node crate, Vidhan taught the compiler to speak html!
https://lib.rs/crates/html-node
Making queries like this checks the sql is valid at compile time by connecting to the real database and running it with demo data inside a rolled-back transaction!