Live data from Hacker News

JavaScript Rising Stars 2020

risingstars.js.org

31–40 of 70 posts

Re: JavaScript Rising Stars 2020

#32
post #18

As a somewhat fad averse engineer who has more or less settled into his own preferred toolchain for FE and BE JavaScript, I plan to invest some time in next.js, tailwind and emotion soon ish. Great to see the state of the art still being pushed. Might see how feasible porting my existing nodejs projects to deno is too.

I tried a deno port, but lack of crypto support was a showstopper. I think I could’ve done it if not for that. It’s quite a lot nicer than node, though, and I definitely will give it another go when it’s further along.

Re: JavaScript Rising Stars 2020

#34
Anyone using React Query in production?

I've got ongoing projects using redux+axios, apollo client, and roll-your-own data fetch hooks. No clear winner in my book. React Query looks neat but have yet to try it.

Re: JavaScript Rising Stars 2020

#35

I shunned the JS world for a while after jumping on the Meteor bandwagon a few years ago and seeing it just fizzle out to a boat load of outdated and unsupported dependencies. Rails was just so much more productive and easy for solo work. But recently I built a couple of services in typescript and the ecosystem seems to have stabilised a lot, my productivity was super high and I’m majorly impressed.

It’s almost a reflection of framework trends, which is not interesting.

Re: JavaScript Rising Stars 2020

#36
post #33

I honestly thought when they said "rising stars" they meant new, awesome projects. Instead it's the same old stuff everyone knows ranked on a metric that is tenuous at best.

Yeah, I wouldn't really consider many of these to be "rising stars". There were definitely some interesting libraries on here that I'd only heard mention of or not at all, but in what world are Angular or Node.js or even React "rising stars"?

Re: JavaScript Rising Stars 2020

#37

Earlier quoted context omitted.

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.

Agreed, TS is a big productivity boost and is here to stay, definitely worth investing time into if you want to get further into JS ecosystem.

You can safely ignore Deno for the time being.

Re: JavaScript Rising Stars 2020

#38
post #34

Anyone using React Query in production? I've got ongoing projects using redux+axios, apollo client, and roll-your-own data fetch hooks. No clear winner in my book. React Query looks neat but have yet to try it.

Also checkout SWR https://swr.vercel.app/

Re: JavaScript Rising Stars 2020

#39
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…

Deno is still incompatible with JS ecosystem

Now is possible to use many NPM packages in Deno, find out on the Web

Re: JavaScript Rising Stars 2020

#40
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…

Now is possible to use many NPM packages in Deno, find out on the Web
Post reply on HN