React
Collections
- A Visual Guide to useEffect
Side effects shouldn’t happen during component render. Therefore they do not belong to the body of a functional component. React has a special place for them.
- 🌠 Some reasons for disliking react hooks
- React - The Missing Parts
- Microsoft Office rewrite in React.js nears completion
- The Perils of Rehydration: Understanding how Gatsby/Next manage server-side rendering and rehydration
- A Visual Guide to React Rendering - Cheat Sheet
- React with TypeScript Cheatsheet. An answer to all your React typing…
- Avoid React Re-Renders with Automatic Batching: batching is not applied to cases like promises, setTimeout, native event handlers, and so on by default. Starting from React 18, there is a new root API called createRoot which allows you to use all the concurrent features of React 18.
- REACT: USESTATE VS USEREDUCER: see section of
Comparing the two implementations - The React Cheatsheet for 2022
- Hooks Considered Harmful (factorialhr.com)
- Why React Re-Renders
- Blogged Answers: A (Mostly) Complete Guide to React Rendering Behavior
- Can We All Just Admit React Hooks Were a Bad Idea?
- Is React going anywhere?
- Aghiles Ait lounis
The real question is not about React going somewhere, some of the alternatives are not “slightly better” rather immensely better, you know that a big company in Brazil is using Svlete for embedded UI for arduino devices not so powerful, performance is a big thing, as devs we want to build the best application possible, we are not business mens looking for turnover, I’m a React developer myself and work as a freelance on a big React project, and let me tell you, if the project was written in Solid it will be 10x easier to maintain, just because of the app re-rendering all the time due to useEffects() thrown everywhere and non memoized functions, objets…it’s a complete mess, anyone that think it’s not big for me it’s because they didn’t work on a big project.
Thus said i might be completely wrong, but for me i found that Svlete, Solid and Qwik are a superior alternatives, especially Solid, they offer you free optimized code without you thinking about anything, your app will be fully optimized out the box ! it’s huge
- Aghiles Ait lounis
- A HISTORICAL REFERENCE OF REACT CRITICISM
- Why Create React App exists
- New React docs pretend SPAs don't exist anymore
The strongly recommended way to start a new React project is to use a framework such as Next.js, while the traditional route of using bundlers like Vite or CRA is fairly strongly discouraged.
- The Interactive Guide to Rendering in React
- An Ode to React Effects
Most of the problems with
useEffectare rooted in bad software design, not the hook’s API.
Performance
- Before You memo()
- Solution 1: Move State Down
- Solution 2: Lift Content Up
- Understanding React Concurrency
- The basic premise of React concurrency is to rework the rendering process such that while rendering the next view, the current view is kept responsive.
- How React 18 Improves Application Performance
Opinions
You’ll Write Less Code With Svelte 5.0, Promises Rich Harris
Harris discussed his perspective on React Server Components (RSCs), seeing them as the logical next step in the journey of co-locating HTML, CSS, and JavaScript within components. However, the separation of server and client components in RSCs can be confusing for developers, as it creates two distinct mental models within the same application.
Children