Rendering HTML on the server was kind of how IBM mainframes talked to their 3270 terminals, only that HTML is a lot nicer than 3270 streams and HTTP is human readable.
Server side rendering makes sense for mostly static content, but for web applications, a front end framework and a back-end API are a much better match.
dzonga · · focus · HN ↗
dhh says 37signal's apps for Hey (their email platform moving to native)
backend for their email platform is now Rust - written by agents
says Rust produces small binaries - cutting number of servers needed from 110 to 10. hell they could serve peak traffic on a Raspberry Pi
says now that agents write all the code - use faster / native languages.
rails or ruby hardly get a mention besides that they might be well placed to capture web apps written by agents.
lackoftactics · · focus · HN ↗
rbanffy · · focus · HN ↗
Server side rendering makes sense for mostly static content, but for web applications, a front end framework and a back-end API are a much better match.