Manjunath M
Aug 13, 2021 ⋅ 7 min read

5 things not to do when building React applications

Manjunath M Writer. I like strings. I like coffee. I like to code.

Recent posts:

Parsing PDFs in Node.js

Parsing PDFs in Node.js

This guide covers the top npm packages for parsing PDFs in Node.js, including pdf-parse, pdf2json, and pdfreader.

Chibuike Nwachukwu
Mar 4, 2024 ⋅ 7 min read
Implementing In App Updates For React Native Apps

Implementing in-app updates for React Native apps

Implementing OTA in-app updates in React Native apps can streamline the update process, preventing delays that hinder overall productivity.

Nelson Michael
Mar 1, 2024 ⋅ 7 min read
Exploring Stylex And The New Generation Of Styling Libraries

Exploring StyleX and the new generation of styling libraries

StyleX is a build-time, type-safe CSS-in-JS library recently open sourced by Meta. Explore StyleX and the evolution of styling libraries.

Ibadehin Mojeed
Feb 29, 2024 ⋅ 9 min read
Building High Performance Ecommerce Sites With Astro

Building high-performance ecommerce sites with Astro

Learn to set up a completely custom Astro ecommerce implementation that’s also highly performant and type-safe in this straightforward guide.

Onuorah Bonaventure
Feb 28, 2024 ⋅ 64 min read
View all posts

4 Replies to "5 things not to do when building React applications"

  1. Shouldn’t `showHiMessage = this.showMessage(‘Hi’)` in the last example be

    `showHiMessage (e) { console.log(‘Say Hi’, e); }`

  2. Hi- if a parent component re-renders, all of its children are also re-rendered, correct? Therefore, how does passing a closure as props to a child cause a performance decrease? Wouldn’t the Button component re-render every time SayHi component renders, regardless of if a closure is passed?

  3. I obsessive compulsively write clean and tidy HTML and I’m being forced to use react, and it seems like react was deliberately designed to piss me and others like me off. Why is it so messy?

Leave a Reply