Live data from Hacker News

Svelte took #1 spot in State of JavaScript 2020 survey

twitter.com

1–10 of 11 posts

Re: Svelte took #1 spot in State of JavaScript 2020 survey

#2
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

Re: Svelte took #1 spot in State of JavaScript 2020 survey

#4
post #2

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 'roadma…

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?

Re: Svelte took #1 spot in State of JavaScript 2020 survey

#5
post #2

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 'roadma…

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.

Re: Svelte took #1 spot in State of JavaScript 2020 survey

#6
post #5

Earlier quoted context omitted.

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.

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.

Re: Svelte took #1 spot in State of JavaScript 2020 survey

#7
post #5

Earlier quoted context omitted.

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.

Re: Svelte took #1 spot in State of JavaScript 2020 survey

#8
post #2

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 'roadma…

So, how did your evaluation go? I mean the real evaluation, experience of coding, building an app, deploying it?

Re: Svelte took #1 spot in State of JavaScript 2020 survey

#9
post #5

Earlier quoted context omitted.

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.

Funding is about $30,000 a year: https://opencollective.com/svelte#category-BUDGET
Post reply on HN