Svelte took #1 spot in State of JavaScript 2020 survey(twitter.com)
twitter.com
Svelte took #1 spot in State of JavaScript 2020 survey
https://twitter.com/SvelteSociety/status/1349248808585056257
10 comments
My favourite stat is that usage essentially doubled since 2019. Hearing that developers want to try Svelte is fairly common now but adoption is what drives an ecosystem of plugins/libraries, educational content and jobs.
Some food for thought (found during a quick evaluation of Svelte for future projects)
Contributors
https://github.com/sveltejs/svelte/graphs/contributors
See main three graphs.
Roadmap
https://github.com/sveltejs/svelte/issues/622
> (last comment - Jun 28, 2020) This isn't really an up to date of view on where we are and where we would like to go. We have some tentative plans to improve how we communicate the 'roadmap' in the future. We'll update when we know more.
https://github.com/sveltejs/svelte/issues/3704
> Honestly the roadmap for the near future is the same as it's been since Svelte suddenly got much more popular without a corresponding increase in maintainer resources: fixing bugs. Developing exciting new features is going to take a back seat to dealing with the huge backlog of issues for the time being.
From original Svelte author:
https://twitter.com/Rich_Harris/status/1341076126475710465
> [...] if you do this on a github repo i'm involved with because you're dissatisfied with the help that was given freely and patiently by other contributors, i will make a mental note of who you are so i can ensure you never get my help, ever
https://twitter.com/Rich_Harris/status/1341167074018795526
> [...] believe it or not I don't spend my time waiting around to be summoned by people expecting me to do free work for them
Contributors
https://github.com/sveltejs/svelte/graphs/contributors
See main three graphs.
Roadmap
https://github.com/sveltejs/svelte/issues/622
> (last comment - Jun 28, 2020) This isn't really an up to date of view on where we are and where we would like to go. We have some tentative plans to improve how we communicate the 'roadmap' in the future. We'll update when we know more.
https://github.com/sveltejs/svelte/issues/3704
> Honestly the roadmap for the near future is the same as it's been since Svelte suddenly got much more popular without a corresponding increase in maintainer resources: fixing bugs. Developing exciting new features is going to take a back seat to dealing with the huge backlog of issues for the time being.
From original Svelte author:
https://twitter.com/Rich_Harris/status/1341076126475710465
> [...] if you do this on a github repo i'm involved with because you're dissatisfied with the help that was given freely and patiently by other contributors, i will make a mental note of who you are so i can ensure you never get my help, ever
https://twitter.com/Rich_Harris/status/1341167074018795526
> [...] believe it or not I don't spend my time waiting around to be summoned by people expecting me to do free work for them
So, how did your evaluation go? I mean the real evaluation, experience of coding, building an app, deploying it?
So are you saying that you're concerned by the lack of a detailed vision for Svelte, or that you're concerned with the behavior of the primary maintainer of Svelte?
My main concerns as a "technology buyer" are (from what I found online with a rapid search): lack of funding, currently only two main committers (the original author not among them), project apparently in bugfixing-only mode, and the original author online attitude.
From an outsiders perspective, that's fair enough. However, Rich's time and focus as well as a number of other maintainers is currently on Svelte-Kit, which gets a commit around every 6 minutes at its peak, and at least every hour otherwise. Rich is ridiculously active.
Your comments are fair, but misguided.
Your comments are fair, but misguided.
I've seen some of the GitHub issues that Rich is referring to in those tweets. They're almost always cases where someone is asking for some feature or change in Svelte and the core contributors disagree that it fits with the design and vision of the project.
Then the OP tags Rich in the hopes that he will swoop in and and override the decision. It's almost always more of a tantrum than a real request for help.
As far as project progress, most of the recent work has been on SvelteKit, but I've been using Svelte for about a year now and it has steadily gained features during that time. It's definitely not in bugfix-only mode.
Then the OP tags Rich in the hopes that he will swoop in and and override the decision. It's almost always more of a tantrum than a real request for help.
As far as project progress, most of the recent work has been on SvelteKit, but I've been using Svelte for about a year now and it has steadily gained features during that time. It's definitely not in bugfix-only mode.
Funding is about $30,000 a year: https://opencollective.com/svelte#category-BUDGET
Ah, I see. That wasn't explicitly stated in your original comment, so I was just wanted to clarify.
I think these are valid concerns about Svelte's future. However, you should give it a try and see if you like it regardless. Its got some neat ideas.
I think these are valid concerns about Svelte's future. However, you should give it a try and see if you like it regardless. Its got some neat ideas.
[deleted]