2022-09-16
2525
#react
Aditya Agarwal
850
Sep 16, 2022 â‹… 9 min read

React render props vs. custom Hooks

Aditya Agarwal Loves experimenting on the web. You can follow me on Twitter @hackerrank.

Recent posts:

how API client automation can save you hours in development

How API client automation can save you hours in development

Learn how OpenAPI can automate API client generation to save time, reduce bugs, and streamline how your frontend app talks to backend APIs.

Lewis Cianci
Jul 1, 2025 â‹… 7 min read
Interface Segregation Principle

SOLID series: Understanding the Interface Segregation Principle (ISP)

Discover how the Interface Segregation Principle (ISP) keeps your code lean, modular, and maintainable using real-world analogies and practical examples.

Oyinkansola Awosan
Jun 30, 2025 â‹… 7 min read
​​How HTML’s Selectedcontent Element Improves Dropdowns

​​How HTML’s <selectedcontent> element improves dropdowns

is an experimental HTML element that gives developers control over how a selected option is displayed, using just HTML and CSS.

Temitope Oyedele
Jun 27, 2025 â‹… 6 min read
advanced caching in Node.js with Valkey

How to get faster data access in Node.js with Valkey

Learn how to implement an advanced caching layer in a Node.js app using Valkey, a high-performance, Redis-compatible in-memory datastore.

Muhammed Ali
Jun 27, 2025 â‹… 7 min read
View all posts

5 Replies to "React render props vs. custom Hooks"

  1. “Classes are hard for humans as well as machines” How did you said this term? Because developers who have used to work in OOPS programming languages (like java, c++) doesn’t face the difficulty to understand CLASS. Can you explain it please?

  2. Good examples and code in this article. Thanks for sharing your thoughts, and keep up the great work 🙌

  3. > Using the render props pattern here would be a mistake because it’s intended to share data between components. So, in this case, we should avoid using render props.

    It seems that button from the example may require some data that’s handled by CardComponent. Would that still be a mistake?

Leave a Reply