Issues » #334
#334 – December 13, 2021
So many React Form libraries out there, and so little time - how should one choose? Check out 5 very important things to look for in a form and learn why KendoReact ticks all the boxes.
this week's favorite
WebGL is the magic sauce behind Solar Storm , an audio-reactive music video that renders live in the browser. After fumbling around with Three.js for many years, WebGL finally clicked for me thanks to React Three Fiber. That’s because I could use the familiar concepts—components, props, hooks and state—and transfer my app development skills to 3D graphics.
With the recent update to Rust, it is time to relook at using Rust and React together. I have a new found love for Rust and everything it can do as a language. One of its more impressive features is its ability to write WebAssembly(Wasm) without much overhead. I have explored how to use Rust to write Wasm before (Blog post coming soon!). But I wanted to see how easy it would be to integrate it into a standard React workflow.
In client-side rendering, the app is rendered by the client. When a browser receives a request for a page, it sends HTML, CSS and, JS code to be run in the browser. The script is loaded and the app becomes interactive. This is a way by which most of the apps are rendered.
The following are quick tips to increase performance in your React application by understanding re-rendering and memoization. To better understand the following tips it’s important to know when React re-renders components. Generally, a re-render is caused by a component’s props or state changing. When a component re-renders all of its children components will also re-render, unless they are memoized.
Why does this happen and what tools does React offer to solve this problem?
Join over 21,200 readers for a free weekly email with fresh news, articles and tutorials.