Why Gatsbyjs Failed to Deliver: The Shocking Truth

Is Gatsby dead? Ever wondered what happened to that once promising star of the Jamstack community - GatsbyJS? Dive into this video to unravel the mystery of the rise and fall of GatsbyJS in the world of react-based static site generators. Be sure to share this one!
Uncover the journey of Gatsby, as it skyrocketed from a whopping $3.8M funding in 2018 to its acquisition by Netlify in 2023, and the unfortunate mass layoffs later that year. Explore how Gatsby, once the poster child of successful OSS startups, lost its market share and faded from its glory.
This video also delves into the turning point for Gatsby - the rise of stronger alternatives like Vercel's Next.js. Get insights from popular developer surveys, GitHub repo, npm trends, and more.
Don't forget to share your thoughts in the comments section. Have you ever built something with Gatsby? Would you continue using it or migrate to a more popular option like Next.js or Astro? I would love to hear from you!
Past Videos:
🔧 Why Every Web Developer Needs To Use This Debugging Tool: • Why Every Web Develope...
🎯 Master Debugging with Chrome DevTools: • Master Debugging with ...
🚀 You're Debugging React Wrong, Let's Fix It: • You're Debugging React...
🤖 ChatGPT Scripting for Beginners: Automate Your Daily Problems (No Code): • ChatGPT Scripting for ...
🐚 A Beginner's Guide to Zsh: Getting Started with the Best Shell: • A Beginner's Guide to ...
🚀 Nextra 2.0 just Launched - Could it be the ultimate static site generator? • Nextra 2.0 just Launch...
⏱️ PREACT Signals: Everything you need to know in 15 minutes: • PREACT Signals: Everyt...
#GatsbyJS #Jamstack #Netlify
━SOCIALS━
instagram ➭ / siwalikm
twitter ➭ / siwalikm
twitch ➭ / codewithsiwalik
━COMMUNITY━
discord server ➭ / discord
🎵 Background music via www.FesliyanSt... 🎶
sub count: 448

[@olivtassinari]

To be fair, Gatsby DX was behind from the beginning when compared to Next.js (2018). I was expecting raising that much money could really tip the balance in favor of it, but Tim's leadership on Next.js has been nothing but exemplary.

[@siwalikm]

True that, they let the community down to be the least. Btw big fan of your work and I'm having a fan moment now :)

[@Coufu]

I'm upset because a good number of projects 4-5 years ago, my team banked on Gatsby because it seemed more mature in the static site generation over nextjs AT THE TIME. So now I have all this tech debt (sites running on Gatsby) lying around that I have to start thinking about migration paths for. I'm sure the Gatsby sites will continue to run and work for the forseeable future since we haven't been leveraging the newest Gatsby features due to questions about support/quality. But still, choosing Gatsby back in the day meant choosing the framework that would continue to pioneer the future of jamstack. Obviously these days, that's not the case.

[@candentmind]

If you need some extra hand to refactor legacy gatsby codebase into more modern platforms or perhaps just for maintaining the legacy code.. you can reply here and let's connect.. I loved gatsby and used it a lot, too bad it didn't quite burgeon into a stronger force to be reckoned with

[@HikaruAkitsuki]

That is why when I try Gatsby this afternoon, npm can't it run run anymore. I try to start with Gatsby-Bootstrap Temple but almost every module was error.

[@siwalikm]

Glad you found this helpful but npm not running is unlikely. Check your node version is same as the project's.

[@HikaruAkitsuki]

@@siwalikm Well I don't know. When I gonna start from scratch, I need to set up my github on my terminal on Fedora which is I'm not figure out yet. When I clone a repo on the github, I'm flooding up by error for no reason. Maybe I gonna research this next time. Now I'm just using Vite and Express for the meantime.

[@siwalikm]

Good choice 🚀

[@jwoods9659]

@@siwalikmNaa they are correct, They are NOT updating Gatsby and if you pull your project from github yarn and npm wont work. You have to spin up a new project. I love Gatsby but its time to let it go.

[@phantomsoul2301]

one question astro can beat next js not in near future but in coming year ?

[@siwalikm]

Maybe but my vote is with Next. :)

[@richardhunter132]

I had no idea. I always struggle to keep up with what's going on in the front-end space, outside of my immediate bubble

[@siwalikm]

Its not just you and that's very probable considering how fast the frontend tech space moves.

[@siwalikm]

Have you ever built something with Gatsby?

[@kitty_chick8570]

I did this in gatsby. i quite like gatsby :) klubbguiden.se/stockholm/

[@guled669]

I have tried it multiple times, but It never clicked with me like Astro did. Even though I know react and graphql it always felt off here I much perfer astro not forcing you into this javascript frameworks, in fact I'm writing vanilla js and vanilla css at most

[@phantomsoul2301]

Vercel took market of netlify then they killed gatsby

[@BobD6502]

too many whooshing and clicking noises, and music is too loud at some points.

[@siwalikm]

I'll took a note of your ASMR preferences Bob 😉