gatsby
gatsby copied to clipboard
gatsbyjs
Is Gatsby discontinued? Please upvote for clarification.
Hi @pieh!
Could you please share your thoughts on this issue and provide insights into the current state of Gatsby? It seems like your are one of the few people still contribution / work of the pull requests.
Do not get me wrong but its actually a bit scary that a repository near to 55k stars feels that discontinued.
I know Gatsby was acquired due to its innovative Data Layer, but many people including me depend on the Gatsby framework as whole.
I would be happy to hear that there are plans for further framework development, although this seems unrealistic to me since Netlify fired nearly every contributor of this repository.
Originally posted by @schettn in https://github.com/gatsbyjs/gatsby/issues/38483#issuecomment-1806786898
However, it's common for open-source projects to have fluctuations in activity and contributors over time. The concerns you've raised about the apparent decrease in contributions and the impact of changes in contributors are valid. Open-source projects can sometimes face challenges, including shifts in maintainer resources, changes in project priorities, or adjustments due to acquisitions.
If you're concerned about the state of Gatsby, I recommend checking the official communication channels for the latest updates. This could include the project's GitHub repository, official blog posts, or community forums. Developers and maintainers often provide insights into the project's direction and address concerns raised by the community.
If there are any recent developments or changes in the project's status, you're likely to find relevant information from official sources. If you have specific questions or issues, reaching out to the Gatsby community directly might provide more detailed and up-to-date information.
Remember that the open-source landscape can be dynamic, and projects may evolve based on community contributions, maintainers' efforts, and overall project goals.
Hey all,
Gatsby is here to stay and we’re not sunsetting it. We’re committed to not only maintain it but also to building a forward-looking roadmap for it as we go into 2024, which I’ll share with you all as soon as we can.
A large part of our enterprise customer base depends on Gatsby for their core properties, as it’s a battle-tested framework used for lots of large, real-world, high performing websites. We’re here to support that, as well as to work with the larger community around Gatsby.
It is no secret that Gatsby is no longer the hip new framework on the block. Our core focus for it now is three-fold:
- First, ensure stability, predictability and good performance.
- Second, give it new powers by strong integration with all new tooling that we add to our Composable Web Platform (for more on what’s all that, you can check out our homepage).
- Third, make Gatsby more open by decoupling some parts of it that were closely tied to proprietary cloud infrastructure. The already-released Adapters feature is part of that effort.
Note: the above focus does mean that Gatsby isn’t going to be the first mover in new rendering paradigms. When it comes to features like React Server Components, Server Actions, etc., we would wait till the best practices have emerged and actual value is clear before making implementation plans.
While we don’t plan for Gatsby to be where the main innovation in the framework ecosystem takes place, it will be a safe, robust and reliable choice to build production quality websites and e-commerce stores, and will gain new powers by ways of great complementary tools.
Over the last few years, Gatsby’s static-first approach guaranteed high performance and uptime for customers, while allowing teams to build compelling front-end experiences.
Our aim to make sure that this is still the case over the next few years.
That's great to hear. In the meantime, perhaps opening up to some of the community who wants to contribute would also be helpful. I wouldn't mind starting to put together some moderation for the Discord: which has become 100% spam, drowning out any real discussion or concerns.
Furthermore there are people (including myself) opening up tickets and pull requests to improve Gatsby that are not getting any attention or feedback. The number of tickets with the triage needed tag is getting overwhelming.
it will be a safe, robust and reliable choice to build production quality websites and e-commerce stores, and will gain new powers by ways of great complementary tools
Hi @biilmann, Thanks for the update. Our main source of anxiety is something like gatsby-source-shopify. Will plugins like this actively track and be updated to reflect API changes in Shopify itself, or would now be a good time to start looking at alternative ways of sourcing that data?
Edit: would it be in Shopify's interest to maintain this plugin themselves, similar to how Sanity maintain theirs?
That's great to hear. In the meantime, perhaps opening up to some of the community who wants to contribute would also be helpful. I wouldn't mind starting to put together some moderation for the Discord: which has become 100% spam, drowning out any real discussion or concerns.
Furthermore there are people (including myself) opening up tickets and pull requests to improve Gatsby that are not getting any attention or feedback. The number of tickets with the
triage neededtag is getting overwhelming.
This is what shocked me, too.
The state of the Gatsby Discord is so bad it should be shut down. Dozens of inactive channels, whose last posts are crypto scams, predatory junior developer job hunting scams or other spam. If the Discord is full of content that goes against the Code of Conduct, why even continue running it at all?
It is no secret that Gatsby is no longer the hip new framework on the block.
It's a real shame because I was an avid fan of Gatsby, but I imagine the main contributing factor of this is mainly the result of the acquisition of Gatsby for Valhalla, which led to downsizing of the entire core team and poor communication around the Gatsby open-source future.
The other important factor, as others have pointed out, is that the open-source nature of the project is pretty dead if no one can contribute, and the only things being contributed seem to be Netlify specific. Plugin maintainers will give up and move on, leaving the eco-system dead in the water.
@biilmann You mentioned stability, but a fresh install and setup with Gatsby has broken dependencies, some around Netlify CMS (which is worse given that Netlify owns Gatsby).
It certainly doesn't inspire confidence in what seemed to be the go-to choice for SSG with React.
I'm glad to hear that Gatsby still kicking. Unfortunately I'm having a hard time right now with this issue, to the point that it gets very frustrating to develop. Coding with Gatsby used to be such a breeze :(
Nevertheless, it's an awesome framework, it deserves some love, and I hope it overcome this challenging period.
I'm glad to hear that Gatsby still kicking. Unfortunately I'm having a hard time right now with this issue, to the point that it gets very frustrating to develop. Coding with Gatsby used to be such a breeze :(
Nevertheless, it's an awesome framework, it deserves some love, and I hope it overcome this challenging period.
im getting this also intermittently. And loads of other various / random / spurious issues (most of which you can see listed as issues but without any resolutions, or even comments in most cases). It seems no matter what Netlify are claiming above, Gatsby is not in a good place.
Having to decide on what to use for our next project and even though I love gatsby it has seen a sharp decline in trust and activity since the netlify takeover. I don't believe a word that was said above about "new powers". Bunch of corporate bullshit.
Going into Q2 of 2024 with zero updates since Q4 last year, I think we can safely assume that Gatsby has been abandoned. It's really a shame, as I have been a huge fan and advocate for years now. But after such a long gap in updates, I can't in good conscience start another project on this framework.
Goodbye Gatsby, and thank you to all the developers who dedicated their time to building something that was wonderful while it lasted.
Going into Q2 of 2024 with zero updates since Q4 last year, I think we can safely assume that Gatsby has been abandoned. It's really a shame, as I have been a huge fan and advocate for years now. But after such a long gap in updates, I can't in good conscience start another project on this framework.
Goodbye Gatsby, and thank you to all the developers who dedicated their time to building something that was wonderful while it lasted.
I am embarking on a new project and am feeling the same.
Going into Q2 of 2024 with zero updates since Q4 last year, I think we can safely assume that Gatsby has been abandoned. It's really a shame, as I have been a huge fan and advocate for years now. But after such a long gap in updates, I can't in good conscience start another project on this framework. Goodbye Gatsby, and thank you to all the developers who dedicated their time to building something that was wonderful while it lasted.
I am embarking on a new project and am feeling the same.
im wondering what to use next for my SSG wordpress type projects? Astro or Next.js i guess?
I have been seeing less and less examples on how to implement new features in gatsby. All the docs still reference gatsby cloud (which has since been shut down).
The major sell of a framework and an ecosystem around it is that someone usually has already done and written about what I want to do.
Not so the case anymore. Major CMS players like Sanity haven't published updates for gatsby specific plugins in over a year at this point.
I think the writing is on the wall.
We have already changed our policy on what to use for new clients and will be migrating away for old ones once we can.
There was only one dev left back when they took over and I doubt that person is around still.
FWIW, since the last release on December 18th, 2023, there have been 63 Commits. Of those commits,
-
28are automated dependency fixes (renovate[bot]) -
13are manually dependency updates or minor misc chore (marked withchore) -
12are fixes (fix) -
7are automated changelog updated (gatsbybot) -
2are a fix to documentation (fix(docs)) -
1is a performance enhancement (perf)
The last actual feature implemented was on Nov 3, 2023 implementing a generator for image and file CDN URl's
The takeaway here is the following: Actions speak louder than words. Based on the actions (and lack of communication), Gatsby is effectively being held in steady state and they are not looking to rock the boat. This is essentially what @biilmann said in his post above:
While we don’t plan for Gatsby to be where the main innovation in the framework ecosystem takes place, it will be a safe, robust and reliable choice to build production quality websites and e-commerce stores, and will gain new powers by ways of great complementary tools.
In summary, I'd say don't expect there to be much movement in Gatsby other than keeping it stable. Any developers / community managers please feel free to jump in and clarify 🙏
It is no secret that Gatsby is no longer the hip new framework on the block.
we don’t plan for Gatsby to be where the main innovation in the framework ecosystem takes place
IMO the current README tagline ”The future of web development is here” should be changed to something else to reflect this new direction for the project. Any ideas?
It is no secret that Gatsby is no longer the hip new framework on the block.
we don’t plan for Gatsby to be where the main innovation in the framework ecosystem takes place
IMO the current README tagline ”The future of web development is here” should be changed to something else to reflect this new direction for the project. Any ideas?
"we've let this die, move along"?
“This died due to colateral from buying out our competition.”
On Sat, 25 May 2024 at 10:40 AM, cordial @.***> wrote:
It is no secret that Gatsby is no longer the hip new framework on the block.
we don’t plan for Gatsby to be where the main innovation in the framework ecosystem takes place
IMO the current README tagline ”The future of web development is here” should be changed to something else to reflect this new direction for the project. Any ideas?
"we've let this die, move along"?
— Reply to this email directly, view it on GitHub https://github.com/gatsbyjs/gatsby/issues/38696#issuecomment-2130600934, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGRIF3EGWNHASJA5QCQSX3ZD7MWPAVCNFSM6AAAAAA7HF5PZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZQGYYDAOJTGQ . You are receiving this because you commented.Message ID: @.***>
I like using Gatsby to build websites. My experience with it has been better recently than in the early days when Gatsby was the "hip" frontend framework. With Gatsby 3 and prior version the debugger window would open up for no reason sometimes and it would be next to impossible to identify the reason. This time around after upgrading the version though it's smooth and I like that it manages so many things to make the website a simple server side rendered site while letting me use my favourite react libraries.
ensure stability, predictability and good performance.
This sounds great. I hope this plan remains. And if there are doubts on this at some point, letting us all know would be great so we can move on in time.
My friend, its dead. You're replying to a post made half a year ago. Move on for your own sake.
Astro. Sveltekit was nice to use but just didn’t work out for anything more than a very basic site. Nextjs or htmx with laravel or go when we aren’t just static.
On Sat, 10 Aug 2024 at 9:16 AM, schwiet @.***> wrote:
What are people using for their new projects?
— Reply to this email directly, view it on GitHub https://github.com/gatsbyjs/gatsby/issues/38696#issuecomment-2278867352, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGRIF52XCRXBDDWPHHYTGTZQVEUDAVCNFSM6AAAAAA7HF5PZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYHA3DOMZVGI . You are receiving this because you commented.Message ID: @.***>