3 ms·
react came out in 2013 so if it survives another year it'll be 10 years already; it's not going to disappear in the next year.
by shishy 4y ago
react came out in 2013
so if it survives another year it'll be 10 years already; it's not going to disappear in the next year.
- weatherlite 4y agoPoint taken you are right. So I wanna see a mainstream FE framework make it to 10 without completely changing its API (Angular, React hooks) or its state management (Redux, Mobix..what is next?) If you know Rails or Django fast forward 9 years.. you still know them. Can you say the same about React?
- acemarke 4y agoFor the record: I maintain Redux, and it's never been an actual recommendation from the React team. In fact, Dan has publicly stated that "the only state management tool we recommend is React itself". Redux is certainly the most widely _used_ state management lib in React apps, but that's a community-driven thing, not anything the React team has specifically suggested (in the same way that React Router is the most commonly used routing lib).
- weatherlite 4y agoOh no doubt. I am not blaming anyone specific here. I'm just calling it as it is - the way you write React apps now will be completely different 10 years from now.
- reducesuffering 4y agoI think just frontend is a more apples to apples comparison. In that scope, what >10 teams >1m ARR are using plain Rails/Django html templates with html button actions and such? If you shop around at Rails/Django jobs, they're almost all going to be using different frontends that you'd need to ramp up on: React, Vue, jQuery, Hotwire, Turbo, Stimulus, HTMX, Alpine.js, etc. You could also say "If you know jQuery fast forward 9 years ago... you still know it" and be right about keeping yourself to the limited opportunities to do it the old-fashioned way.