4 ms·
Nice to see it still around and updated. The sad part is I guess this means React will be around in 2060.
by b3ing 9mo ago
Nice to see it still around and updated. The sad part is I guess this means React will be around in 2060.
- b65e8bee43c2ed0 9mo agothere are already de facto two Reacts. by 2060, there will be five.
- 2muchcoffeeman 9mo agoTwo Reacts!?
- exac 9mo agoAs someone who doesn't use React, there is React Native (for iOS & Android), and React (and that can be server-rendered or client-rendered).
- psnehanshu 9mo agoThere's also React Native Web
- underdeserver 9mo agoI'm sorry what
- rauli_ 9mo agoIn case you want to use React to make Web sites as well.
- afiori 9mo agoI find it is a good idea, it allows developers to cleanly define how to structure elements without random divs sneaking in. It requires a strong design system and it probably makes it harder to use some web APIs but those can be reasonable tradeoffs
- docmars 9mo agoSpeaking of which, is there a Tailwind CSS equivalent for React Native? I find passing `style` objects around (ala CSS Modules) to be a pain after using Tailwind for so long in web projects. EDIT: Found one that's going v5 soon, looks nice. https://www.nativewind.dev/ https://www.nativewind.dev/
- tcoff91 9mo agoTwitter is built in React Native Web
- atulvi 9mo agoThere was also react vr
- tcoff91 9mo agoclass components & function components.
- afiori 9mo agoThat is the least interesting divide in the react community
- o_m 9mo agoThe main divide now is client side React versus Server Components usually with a node.js backend
- mikeaskew4 9mo agoby 2060 React Native should be up to v0.93
- deleted 9mo ago[deleted]
- altern8 9mo agoWhat's wrong with React? It made it so much better to build apps vs. spaghetti jQuery. I still have nightmares about jeeping track of jQuery callbacks
- lopatin 9mo agoThe problem with React is that it solved frontend. So the options are to 1. Code React all day and be happy with it. 2. Come up with reasons why it's bad. There are many talented and intellectually curious people in the field which lean towards 2.
- gmac 9mo agoThe problem with React IMHO is it’s so dominant and so annoyingly over-engineered for many problems. I use Mithril and find it much less fuss.
- docmars 9mo agoWhen they started adding new hooks just to work around their own broken component/rendering lifecycle, I knew React was doomed to become a bloated mess. Nobody in their right mind is remembering to use `useDeferredValue` or `useEffectEvent` for their very niche uses. These are a direct result of React's poor component lifecycle design. Compare to Vue's granular lifecycle hooks which give you all the control you need without workarounds, and they're named in a way that make sense. [1] And don't get me started on React's sad excuse for global state management with Contexts. A performance nightmare full of entire tree rerenders on every state change, even if components aren't subscribing to that state. Want subscriptions? Gotta hand-roll everything or use a 3rd party state library which don't support initialization before your components render if your global state depends on other state/data in React-land. 1. https://vuejs.org/api/composition-api-lifecycle.html https://vuejs.org/api/composition-api-lifecycle.html
- leptons 9mo agoI use Preact, in the old-school way, without any "use-whatever" that React introduced. I like it that way. It's simple, it's very easy, and I get things done quickly without over-thinking it.