3 ms·
The final outcome is the same - static files on a cdn - so it won't always matter but netlify lets you: 1) run a build process 2) own domain with automatic ss
by benologist 11y ago
The final outcome is the same - static files on a cdn - so it won't always matter but netlify lets you:
1) run a build process
2) own domain with automatic ssl and redirecting to w/e www-or-not, https-only etc
3) deploy with git push
4) url rewriting, header inserting, proxying
- ChristianBach 11y agoExactly, and because of the automatic URL rewriting Netlify will also give you instant cache validation. So when you update your site, unlike most static site hosts, you won't have to wait to see your changes live. But at the same time you get a very cached and very fast site. So best of both worlds.