Why WeWork.com uses a static generator

Post by Dr_tldr » Wed, Dec 16, 2015, 12:05 AM UTC

bobfunk wrote: post #40

Dr_tldr wrote: post #37

Some serious questions: 1. Why not just use fs.writeFile to create all the site info as json files as either a one off or a chron job, then run a gulp task to either use something like jade or else roll your own rendering to put the JSON in the right place on the page, then output the result as html to a public folder, set up an express static server and have a catch-all splat after it for 404s? What am I missing her…

For point 1 - that will give you way worse performance than WeWork's current setup, since all requests will have to go back to your origin where your express server is running in order to determine if it's a static request or a dynamic request. With netlify this happens at the CDN PoP which makes a huge difference for a site with a global audience like WeWork.