Hacker News Reader

Comment by lsalvatore | Hacker News Reader

JavaScript framework churn (on the frontend) ended 6 years ago. The only thing keeping this meme going is commenters on HN.

View on HN

What framework did you end with? What state management approach? What styling strategy? I think the churn stops whenever you stop adopting new things to replace functionally equivalent things, but new things still come along and get hyped.

Library: React State Management (if needed): Redux via Redux Tool Kit. Maybe Redux Toolkit Query too if necessary. Style Strategy: SCSS or Styled Components (if I have to) Framework: Remix[0]

This is honestly a very easy set of questions to answer today.

[0] remix.run

Software engineers that replace things with functionally equivalent things don't get a lot of actual work done and typically aren't employed for very long either. So, the churn had to stop long ago from inside the average high performing company (and professional engineer's mindset). Only when things are really bad (as they were 6 years ago) is it worth rewriting everything. We've done that and it's not happening again. You can follow my work here: react.school

So because there's no churn and everything is standardized I assume you can tell me which state management library is the correct choice for a React app without causing any controversy?

Yes, that's easy.

React-Query[0]: You don't need to manage state, let your server manage state just like you do in typical non-js heavy apps.

[0]: https://react-query.tanstack.com

Sure, book a free call with me here: react.school/call

Why not share it in a single 10-word comment here for the benefit if all if it's so uncontroversial.

React, Redux, styled-components.

Reply on news.ycombinator.com