Hacker News Reader

Until an HTML element/CSS feature you are using is rendered obsolete and stops working in Chrome :)

S3 requires an active AWS account with billing, etc., and upload to Netlify implies that you're trusting that Netlify's platform will be free forever.

The requirement was zero maintenance, not zero cost. If you have a web app, a hosting cost is expected.

I think the implication here is that you have to 'maintain your credit card'. Not an issue until you switch banks or have some sort of issue with a corporate card that you use with your AWS account.

I think it's being nitpicky for the purposes of this discussion but I think there are probably several HNers who could tell you about how their product hosted in AWS went down because of a credit card issue.

S3 breaks url format in a backward incompatible way occasionally: https://news.ycombinator.com/item?id=19821406

Otherwise this is definitely the way to go. Nothing beats static files that you can just cp into a bucket.

Exactly what I was thinking. Static content hosted in an environment you don’t have to patch, reboot, worry about things breaking after patches, etc. and the fact it’s static html and css means no runtime config, updating libraries, compatibility issues, etc.