> drop the files in an S3 bucket
If you have a completely static site you still shouldn't host of s3, that's a big no no.
S3 isn't a CDN; you want a CloudFront or something else in front of that.
But as soon as you need something more your gonna get lost or locked in.
I disagree, pages for web apps don’t just CRUD one entity, they mix and match many entities in complicated ways. Also, I was referencing rails auto generated crud pages where there’s a single form and a single entity table.
If that’s all that’s required then kudos but rarely has that been true for the companies I work for. I wish it were true.
Multiple entities with multiple endpoints are harder, if not impossible to enforce.
Having separation between the HTML on the server side and the JS on the frontend side is exactly why React become popular.
Personally, I don't want to go back to the PHP+jQuery days. I want one language and one framework to handle both HTML and JS interactivity.
But did they really. Cuz now i see .jsx files with sql calls, adding in static js and css, and logic with mixed html in... Its honestly blowing my mind how we got to this point.
We all agreed biz logic, and view should be separated. and that html, css, js should also be in sperate files. and then .jsx or the like came along and merged them all back together in some of the ugliest code ive seen in years.
And most of that doesn't need to be.
I would argue that a client-side only SPA is very simple from the lens of how it is deployed: drop the files in an S3 bucket. There’s no need for a server and from that perspective, an SPA is actually a simpler stack.