Is GatsbyJS Officially Dead? #39062
Replies: 5 comments 6 replies
-
|
Following up on this thread. I would really appreciate the maintainers perspective on GatsbyJS future. I have projects that are dependent on this and I need to advise my clients. Any community member thoughts on the health and survivability of GatsbyJS as it lives in the Netlify-ecosystem? (apologies, not trying to pretend Im another account -- Im the OP, just happened to check status while I was in my other account). |
Beta Was this translation helpful? Give feedback.
-
|
It has been abandoned and therefore can be considered dead, see the silence of maintainers on #38696. Next, Astro, Remix are all good alternatives. |
Beta Was this translation helpful? Give feedback.
-
|
As far as I'm concerned, Netlify is losing a lot in terms of reputation for what it's doing with Gatsby. I can't recall another operation so deliberately harmful to the JS community as Netlify's acquisition of Gatsby. An entire team laid off overnight, a SaaS with thousands of active projects trashed, and lots of "don't worry, everything is fine" messages while the building is on fire. I hope for more transparency from the Netlify team in the future, because there's a big difference between saying "Gatsby may no longer be cutting-edge, but we're focusing on stability" and not having a significant commit in almost a year. I still have several projects in Gatsby, and I can't find a valid alternative when it comes to theme shadowing. It doesn't seem like Astro supports it. Do you have any valid suggestions? |
Beta Was this translation helpful? Give feedback.
-
|
I've had it narrowed down to Astro and Next for awhile, but I am very allergic to going Astro for the very simple reason that Astro appears to be a kissing-cousins to GatsbyJS/Netlifys model. Say I run with them and they implode just like Netlify/GatsbyJS - shame on me! |
Beta Was this translation helpful? Give feedback.
-
|
We are actually considering to switch our gatsby-starter-foundation to Astro, how sure are you about this. |
Beta Was this translation helpful? Give feedback.
-
|
Sure about what? Astro going the way of Gatsby? Im not certain of that at all. My comment is entirely fear based given the limited research I've done on Astro. Im not interested in good-willed private enterprises that play the cash-grab game. I'm just looking for a stable framework to deploy to a stable platform. It's going to cost me a lot of time, which is money, to move my projects away from Gatsby. I accept that things like this happen, but the way GatsbyJS/Netlify handled this really doesn't sit right with me and it feels like Im prematurely migrating away from Gatsby when it could have been a viable option for many years to come. For now, I'm personally picking NextJS. Yes... privately owned by Vercel, but my research suggest it's much more versatile than Astro (this all comes from anecdotes off of Reddit -- ask me again in a few months if I made the right choice). The other thing that makes me raise an eyebrow is that Astro has some component architecture that sounds like it may not mix well. AKA going Astro might be a one-way trip that makes migrating away harder? Again, just random threads on Reddit. I feel like that with NextJS I can easily migrate, get back up and running, and if I need to migrate from NextJS to Astro that seems like a possibility. My two (fear-driven and illogical) cents. |
Beta Was this translation helpful? Give feedback.
-
|
I fear to experience with Astro the same I experienced with Gatsby: just to have a very comfortable tool until it goes wrong (my opinion). |
Beta Was this translation helpful? Give feedback.
-
|
I stopped using Gatsby 3 months ago. Netlify is neither an option for future projects. Transparency and stability is what I need. The low activity on issues speak for itself... |
Beta Was this translation helpful? Give feedback.
-
|
We also stopped, now building new template as alternate for gatsby-starter-foundation with Astro |
Beta Was this translation helpful? Give feedback.
-
|
I will not adapt any "in-between" development solution anymore, but use the main JS frameworks. Maybe I am wrong... |
Beta Was this translation helpful? Give feedback.
-
|
What you are saying is correct, initially i considered next.js which is my goto framework. But for static blog astro does the job |
Beta Was this translation helpful? Give feedback.
-
I can't get Netlify to respond, and I read rumors online suggesting the original GatsbyJS team rage-quit or was let-go (whatever) Netlify post-merger -- whatever the facts, I have several GatsbyJS-based projects I need to know if I should migrate to another framework.
Thanks GatsbyJS-residual-team! I miss you guys and hope everything is OK!
Beta Was this translation helpful? Give feedback.
All reactions