2023-06-09
1921
#react
Rico Kahler
2335
Jun 9, 2023 ⋅ 6 min read

react-virtualized vs. react-window

Rico Kahler I’m a React engineer at www.justsift.com. At Sift, I’m responsible for taking the team’s ideas and designs and turning them into experiences.

Recent posts:

Improving Frontend Workflows With In-Browser Database Tools

​​Improving frontend workflows with in-browser database tools

In-browser database tools like RxDB and Neo4j Sandbox help frontend devs manage data, work offline, and streamline tasks with AI support.

Muhammed Ali
Jun 3, 2025 ⋅ 7 min read
How To Iterate Over Enums In TypeScript

How to iterate over enums in TypeScript (with code examples)

Learn exactly how to iterate over numeric and string enums in TypeScript, with practical code snippets and type-safe patterns.

Matteo Di Pirro
Jun 2, 2025 ⋅ 9 min read
How To Import SVGs Into Your Next.js Apps

How to import SVGs into your Next.js apps: A 2025 guide

Learn the best 2025 methods to import SVGs in Next.js 14+, with tips on performance, styling, and App Router integration.

Joseph Mawa
Jun 2, 2025 ⋅ 9 min read
designing llm first products

Designing LLM-first products, not just features

Everyone’s building chat-first AI products. And most of them suck. Here’s how to break the mold and ship LLM-native software that actually solves problems.

Rosario De Chiara
May 30, 2025 ⋅ 4 min read
View all posts

2 Replies to "react-virtualized vs. react-window"

  1. “Without windowing, React has to write your entire list to the DOM before one list item is visible.” This statement although correct is not the entire reason why one should use a virtualized list, imho scrolling is the main reason here. Scrolling a dom list with thousands of nodes feels like you’ll die of old age before you get to the other side.

Leave a Reply