Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JavaScript Rising Stars 2020

risingstars.js.org

Post reply on HN
Print view View original

51–60 of 70 posts

Re: JavaScript Rising Stars 2020

#51

Post by cuddlecake »

ljoshua wrote: post #49
davedx wrote: 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 quite enjoy Tailwind, and have used it in several production projects. When using Tailwind, don't forget that it is not only to be used as a utility-like CSS framework, but is also intended to build your own CSS systems. You can customize it and build your own classes using the `@apply` directive and other tools so that you don't copy/paste the same utility classes all over the place, but instead use CSS as we used…

I personally would recommend against making a lot of custom classes via @apply, especially when pairing with a component based framework like React.

React makes it easy to avoid the need for duplicate naming such as 'btn' css class and a component.

I would also recommend twin.macro, though I'm still on the fence about using it.

At the very least, it helps with difficult things like style overwrites, ensuring utilities are spelled correctly, conditionally applying utilities and bailwind (one-off styles)

Re: JavaScript Rising Stars 2020

#53

Post by vlasky »

albertgoeswoof wrote: post #9

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.

Meteor is alive and well! Since 2015, I have been relying on it to implement a number of SaaS solutions involving real-time location tracking.

In 2016, Meteor 1.3 implemented full support for the NPM ecosystem. As a result, people switched to using NPM packages directly (where possible) instead of older Atmosphere packages.

This common misconception of outdated dependencies may be the result of non-Meteor users browsing the atmosphere website and seeing many old packages.

Re: JavaScript Rising Stars 2020

#56

Post by hombre_fatal »

root-z wrote: 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.

Most niches don’t have multiple popular contenders except for some core concerns. Most of the time you can default to the popular one if you don’t know how to evaluate it any further, but the README and API tend to make the decision trivial. The project with the best docs is an easy deal breaker as it’s a good signal that the engineers have put some hammock time into the project and they have attention to detail.

But also, just try multiple libraries out. Sometimes one library doesn’t even give you the results you want. I notice beginners in general are resistant to that and seem to think precious time is wasted if they don’t make the perfect decision upfront. I say spend an hour playing with various libs if you can’t decide otherwise.

Re: JavaScript Rising Stars 2020

#57

Post by ibejoeb »

acemarke wrote: post #46
ibejoeb wrote: 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.

React Query is pretty cool. I haven't used it in my own projects, but based on all the discussion I've seen, it looks like a solid choice. Meanwhile, we in the Redux team recently published an alpha library that we've dubbed "RTK Query" [0]. It takes inspiration from data fetching libraries like React Query, SWR, Apollo, and Urql, and provides similar sophisticated data fetching and caching capabilities. But, it's bu…

Nice, gonna check out RTK now. Thanks.

Re: JavaScript Rising Stars 2020

#58

Post by acemarke »

ibejoeb wrote: post #57
acemarke wrote: post #46

Earlier quoted context omitted.

React Query is pretty cool. I haven't used it in my own projects, but based on all the discussion I've seen, it looks like a solid choice. Meanwhile, we in the Redux team recently published an alpha library that we've dubbed "RTK Query" [0]. It takes inspiration from data fetching libraries like React Query, SWR, Apollo, and Urql, and provides similar sophisticated data fetching and caching capabilities. But, it's bu…

Nice, gonna check out RTK now. Thanks.

Sure. For RTK specifically, I recommend reading the "Modern Redux with Redux Toolkit" section of the recently rewritten "Redux Fundamentals" core docs tutorial, which shows how RTK simplifies common Redux usage patterns:

https://redux.js.org/tutorials/fundamentals/part-8-modern-re...

And the companion "Redux Essentials" tutorial teaches Redux Toolkit as the default way to write Redux logic while building a "real world"-style example app:

https://redux.js.org/tutorials/essentials/part-1-overview-co...

Re: JavaScript Rising Stars 2020

#59

Post by franklyt »

albertgoeswoof wrote: post #9

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.

Rails is still great for a project between the sizes of small and large, the former and latter of which will benefit from tools with a lighter touch (like Go), in my opinion.
Post reply on HN