Reading this I can't help but be lost trying to come up with any alternative solution for this specific use case that is worse than what they describe? A bunc

Reading this I can't help but be lost trying to come up with any alternative solution for this specific use case that is worse than what they describe? A bunch of mostly static blogs can be hand-edited HTML, or some ancient perl script, or any of the existing static site generators. If it absolutely needs to involve server-side logic, it could be completely accomplished within a single call to ```rails init```, and the resulting project would incorporate a few $billion worth of collective experience commonly refered to as "best practice". It would be far easier to modify and far less likely to contain vulnerabilities. Performance would be worse by a factor of maybe x100, or "why are you asking these weird questions?" when converted to the real world, according to a representative survey of end users. There's a good argument for replacing individual components on, say, the critical path for rendering people's twitter feed with lower-level implementations. But it strikes me as unlikely that such endeavours would care about the ability of their ORM to quickly generate the migration scripts to drop or add some database columns. So I can't quite see the benefit of cramming the rails model into Rust? Rails is spectacular in how it allows you to quickly iterate, adapt your data model, try some ideas, and so on. Those are qualities that just logically do not transfer to a world of static typing and manual memory management.