-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Gatsby with SvelteKit for CWV comparison #1341
Comments
I think the comparison is still a reasonable one to show despite the factors you mention given Gatsby, similar to Astro, was also heavily used for content-focused sites. So the comparison may be helpful to those looking to migrate. I guess the question of whether SvelteKit should also be listed is a separate thing to consider. |
Okay, the Gatsby comparison makes sense due to its popularity for content sites. |
I think it’s OK to rename this issue if you like. I’ll admit it might be a bit tricky to decide how to expand this chart. I wasn’t involved in putting it together, but from my POV it looks like a list of a) content-related competitors (Gatsby/WordPress) and b) very popular JS tools (Next/Nuxt). SvelteKit falls more into a category alongside Remix of being a bit less popular still (than Next/Nuxt) but also not really focused on content. If I had to make a decision I’d be tempted to say 5 is a nice number of tools to show here and not expand beyond this to avoid the chart becoming a list of every available tool imaginable. But I’m also open to hearing why it’s important for another specific tool to be added! |
Our homepage currently displays Core Web Vitals comparison including Gatsby. However, Gatsby has shown signs of a significant decline in maintenance and community support, with official acknowledgment of reduced activity (ref: gatsbyjs/gatsby#38696).
Sveletkit is an actively maintained, modern meta-framework with a strong performance focus and growing adoption.
Proposal:
Replace Gatsby with SvelteKit in our Core Web Vitals comparison chart.
This would make the comparison more valuable for developers making framework choices in 2024 and beyond.
The text was updated successfully, but these errors were encountered: