Hacker News Reader

Yeah, but does your S3 bucket talk about something called JAMStack the whole day? \s

There isn't really an advantage. It is static page hosting. I remember the days when you would just FTP those sites onto a server, serve with Apache and call it a day, but I guess everything needs to be behind a CDN these days.

Even better, a Backblaze B2 bucket fronted by cloudflare because your traffic then is free...

You don't bother with S3 setup (let alone aws setup), static access rules, then cloudfront setup and config, domain binding and ssl setup. You also don't bother with cloudfront cache invalidation.

Netlify abstracts all these things for you, also it stores all the versions you have uploaded or built and gives a quick option to rollback to the specific version.

I'm kind of AWS power user and have no problem with with corresponding terraform templates for S3 hosting, but I prefer Netlify if possible.

The overwhelming reason is easier deployments since it'll build on a git/repo push and roll out automatically with cache invalidation and proper cache headers. Very little config beyond your custom domain name.