61–70 of 81 posts
Earlier quoted context omitted.
Pick a few random sites from the Gatsby showcase on their homepage and run them through webpagetest.org Simple Testing.
shopflamingo.com, ideo.com, ca.braun.com, and bejamas.io are all blazingly fast for me.
First paint: 4.1 Seconds. Time to interactive: 11.5 Seconds.
I wouldn't say that's very fast.
Edit: I didn't check the other three.
Earlier quoted context omitted.
Gatsby is a fairly complex static site generator. At the highest level, it provides an ingest layer that can take any data sources (CMS, markdown, json, images, or anything that a plugin supports) and bring them into a single centralized GraphQL data source. Pages (which are built using React) can query this graph for the data they need to render. Gatsby then renders the React pages to static HTML and converts the qu…
But if you have 16,000 of anything, why are you using a static site? Surely the access patterns are long tail and you need to build more often than most pages are even accessed.
Earlier quoted context omitted.
But if you have 16,000 of anything, why are you using a static site? Surely the access patterns are long tail and you need to build more often than most pages are even accessed.
Cheaper to build a site and dunp files to a bucket than running Wordpress code on every request.
Earlier quoted context omitted.
Gatsby is a fairly complex static site generator. At the highest level, it provides an ingest layer that can take any data sources (CMS, markdown, json, images, or anything that a plugin supports) and bring them into a single centralized GraphQL data source. Pages (which are built using React) can query this graph for the data they need to render. Gatsby then renders the React pages to static HTML and converts the qu…
But if you have 16,000 of anything, why are you using a static site? Surely the access patterns are long tail and you need to build more often than most pages are even accessed.
How much is the speed issue related to the language used? I know Hugo is an order of magnitude faster than most static site generators for example - it's written in Go with e.g. 2 seconds to generate about 10K pages https://forestry.io/blog/hugo-vs-jekyll-benchmark/ . I would have thought the generation process could be massively parallelised and a typical blog page would only need a modest amount of computation e.g.…
I don’t think it’s a language issue. Even for JavaScript bundlers you have the slow extensible bundle and the “new super fast bundler” that dies in a month because it only fits one use case. How flexible is Hugo? And how many plugins does someone generally use?
It does have themes, but I just write my own.
Earlier quoted context omitted.
Server-side rendering (like Wordpress) generates HTML in response to a URL. Static site generators just visit every possible URL at build time and save the final HTML as files. This makes it easy to deploy and scale when your site is static and doesn't need any features of dynamic server-side rendering. Gatsby (and other frameworks) automate this process by going through whatever data sources you have (directory of m…
Wordpress in particular is not “just fine”. During this crisis, every government site based on WordPress ends up crashing under the load. Yes, you can avoid this with a good cache plugin and a CDN. But you can also avoid it by using a tool that is designed to not crash under load in he first place.
Cheaping out on things that need actual support wont be fixed by making it a static html page.
Earlier quoted context omitted.
Cheaper to build a site and dunp files to a bucket than running Wordpress code on every request.
Surely there's a CPU/disk trade off at some point. Static pages are much larger (less likely in memory) and would cause disk reads much sooner than the same files being generated dynamically. Of course wordpress isn't known for it's efficiency so the static page preference is probably quite high.
also the answer to a large number of my interview questions ends up being figuring out how you can just effeciently serve the stuff from a CDN/Blob Storage. You can scale the crap out of this for quite cheap.
Earlier quoted context omitted.
Server-side rendering (like Wordpress) generates HTML in response to a URL. Static site generators just visit every possible URL at build time and save the final HTML as files. This makes it easy to deploy and scale when your site is static and doesn't need any features of dynamic server-side rendering. Gatsby (and other frameworks) automate this process by going through whatever data sources you have (directory of m…
Wordpress in particular is not “just fine”. During this crisis, every government site based on WordPress ends up crashing under the load. Yes, you can avoid this with a good cache plugin and a CDN. But you can also avoid it by using a tool that is designed to not crash under load in he first place.
Sure if you just want to serve HTML files on every request with a simple file server than static files will be faster, but it'll eventually get overloaded too. The CDN is where the real scaling happens. And using a CDN is far easier than changing the entire backend to a static site.
Also most of the sites that crashed were dynamic applications, not just static pages. Using a static site generator wouldn't solve that problem.
so this is cool release, and no objection on that but if your pipeline has automated testing, security scans and more then you are not actually deploying in 10s more technical details would be good but I guess either I missed it or they look at it as IP
Gatsby founder here. Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!
Kyle, Just read the post, congrats on the launch! We've been using Gatsby on: https://mintdata.com for the past few years, and are huge fans of your work. I still recall the day when I brought Gatsby into our org, our front-end guys almost ate me alive :D They said: a React.render(...) + GraphQL thing, why do we need it? What's the big deal? Fast forward a few years later, and Gatsby dominates (in my opinion) the bes…