From Gatsby gridlock to Astro bliss: my personal site redesign
1–10 of 91 posts
Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#2Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#3Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#4Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#5They rode the highs - being the default docs tool for React, and building a massive ecosystem of integrations you could install out of the box. But too many abstractions, divided goals between cloud and OSS, and the better stewardship/design of Nextjs brought it down.
There were the simple lessons (https://swyx.io/a-world-without-plugins-cig). its easy to say in hindsight that graphql was too much for gatsby. i also believe the company went too hard for number of integrations over quality of them, an issue I had even in my interview. this was a poorer expression of the better insight that seb markbage had; just have a small api surface area bro (https://www.youtube.com/watch?v=4anAwXYqLG8)
But the bigger lesson is bitterer. Frontend tooling isnt worth that much. the fact that vercel is pretty much the only successful frontend startup of its generation makes it an exception to the rule (there are plenty of smaller companies that are thriving, like tailwind, but it is not a venture scale startup and thats fine). People dont pay for frontend tooling. they expect it to be free, expect it to do everything, get into internicine squabbles between frameworks when they are all basically doomed compared to just betting on React sponsored by Facebook and now Vercel (and a little bit of Shopify), or going back to fullstack frameworks like Django/Rails/Laravel. all frontend tooling, nextjs included, is just leadgen, loss leaders, while investors/salespeople patiently wait until you "grow up" by... building cloud backend/ci/cd services.
5 years ago i wrote about the "frontend ceiling" for individual developer careers (https://x.com/swyx/status/1682748872047886337) - i fear this is the "frontend ceiling" for companies.
I deeply admire Astro and hope they figure out a way to break the ceiling. Their recent cloud products have been encouraging.
Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#6I am still not over the collapse of Gatsby (for reference i nearly joined the company in 2017, was saved only by my own character flaws). They rode the highs - being the default docs tool for React, and building a massive ecosystem of integrations you could install out of the box. But too many abstractions, divided goals between cloud and OSS, and the better stewardship/design of Nextjs brought it down. There were th…
I think Typescript's websites uses it (or used to), and I wanted to fix a bug in the website and holy hell if Gatsby made me dislike the experience..
Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#7I don’t love js/ts but Astro is so nice. Don’t have to fiddle with react or graphql. Just upgraded to 5 beta and nothing broke. Really well managed project. Oh, and page load speed is insane.
Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#8I am still not over the collapse of Gatsby (for reference i nearly joined the company in 2017, was saved only by my own character flaws). They rode the highs - being the default docs tool for React, and building a massive ecosystem of integrations you could install out of the box. But too many abstractions, divided goals between cloud and OSS, and the better stewardship/design of Nextjs brought it down. There were th…
Cool insight on frontend ceilings -- deployment is king.
Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#9Re: From Gatsby gridlock to Astro bliss: my personal site redesign
#10Great write up, will be curious to see if Astro sticks around. It seems like all the static site gens last a few years then fade away - Jekyll, Hugo, Gatsby, etc.