Live data from Hacker News

JavaScript Rising Stars 2020

risingstars.js.org

21–30 of 70 posts

Re: JavaScript Rising Stars 2020

#21
post #5

I’m currently organizing a roadmap for improving my full-stack skills. I work in JS with Node and React. Does anyone have any opinion on whether I should spend time learning Deno and Typescript instead of digging deeper into what I already know? I find it hard to tell if Deno will start showing up in job descriptions in a few years, or if Node is so entrenched that it would only distract me from building on my curren…

If you only ever worked in JS (browser and/or server), branch out. Try different things instead, it'll make you a better JS developer (and better developer in general) if you try to learn things that are far out from your current skill set. If you're into types, go for Haskell or Erlang. If you're into dynamic runtimes, go for Clojure or Smalltalk.

Re: JavaScript Rising Stars 2020

#22

Surprising not to see EmberJS listed in the front end frameworks. Did it not make top 20 or was it an oversight?

While EmberJS is a solid framework, I don't think it is a "rising star"

Sure, but by that logic React and Angular shouldn't be there either.

Re: JavaScript Rising Stars 2020

#24
The JavaScript community has a huge problem with hype and churning libraries unnecessarily.

Using a metric like "number of new stars" just exacerbates that problem. It neither tells you about libraries are undiscovered gems, or libraries which are proven, stable and reliable.

It's simply a measure of which libraries are well into their hype curve.

Re: JavaScript Rising Stars 2020

#25
post #5

I’m currently organizing a roadmap for improving my full-stack skills. I work in JS with Node and React. Does anyone have any opinion on whether I should spend time learning Deno and Typescript instead of digging deeper into what I already know? I find it hard to tell if Deno will start showing up in job descriptions in a few years, or if Node is so entrenched that it would only distract me from building on my curren…

Master typescript and you will be rewarded greatly! It is a fantastic tool with a very high level of adoption already. It makes React significantly easier to write and refactor. You won’t ever go back to plain .js! Deno is not relevant enough, I would wager 99.99% of the existing projects you might find yourself working on in the next few years will be using node somewhere in the stack. It shouldn’t be hard to pick u…

Yes, this. Use TypeScript with Node and/or React.

Re: JavaScript Rising Stars 2020

#26
Worth noting that this is just measuring the amount of stars a project has, not if you absolutely, must learn this today to stay current. Libraries and frameworks comes and goes, it's your base knowledge you need to improve upon, not specific APIs offered by easy-to-consume libraries and frameworks. Learn them, adopt their best ideas, throw away the rest, pick the right tool for the job, probably the best tool is not the tool you're currently most familiar with, if you rank your choices based on GitHub stars anyway. People use stars for all kinds of purposes, don't extract "It's valuable" because of that.

Re: JavaScript Rising Stars 2020

#28
I come from a JVM/Python background, so not familiar with JS ecosystem at all. How do people decide what to use when there are 5 most popular libraries/frameworks in each category. Not saying the diversity is a bad thing. Just wondering how people make these choices when starting a new project.

Re: JavaScript Rising Stars 2020

#29

https://2020.stateofjs.com/en-US/ is a bit more useful.

As someone who hasn't touched JavaScript much since the 90's I found the original article linked quite useful as straight away I was able to see the relevant tech stack cf. the 2020 link.

Re: JavaScript Rising Stars 2020

#30
post #28

I come from a JVM/Python background, so not familiar with JS ecosystem at all. How do people decide what to use when there are 5 most popular libraries/frameworks in each category. Not saying the diversity is a bad thing. Just wondering how people make these choices when starting a new project.

If all else is equal, I opt for the smallest contender (in terms of minified size). I also check the dependency graph and nope out if it’s unreasonably large.
Post reply on HN