or subscribe with
Join 8,000+ readers for one email each week.
Digests » 351
In this post, we will be creating a survey website with the help of Remix framework and KendoReact. Learn how to speed up app development and offer amazing UI and UX.
this week's favorite
This post will explore how we integrated this WASM code into a React/Redux application, as well as why we ended up writing our own bindings generator for it.
React 18 adds out-of-the-box performance improvements by doing more batching by default, removing the need to manually batch updates in application or library code. This post will explain what batching is, how it previously worked, and what has changed.
We use React to make reusable components that can be used in a logical way to make UI. Making components in React is as easy as making a function.
Components fetch data, respond to user interactions, and manage app state. To verify this functional behavior, developers rely on automated tests. But most testing tools are Node and JSDOM based. That means you’re forced to debug visual UIs in a textual command line.
Normally I am not a big fan of drilling down to the implementation details and you certainly don't need to know that in order to be productive in React. However, when it comes to understanding the rendering behaviour and rules for bailing out of re-renders, the React docs haven’t provided a thorough enough explanation to satisfy me.