reakit VS react-virtualized

🔍 Site ⭐ GitHub

Typescript is a mistake. Static typing seemed like such a potentially good thing to add to javascript, but the reality is it's a nightmare to work with. If you don't believe me, go to Reakit's github and tell me the complete set of valid options for creating a tooltip.

As a tech lead (or whoever makes the technical decision), it looks very tempting to adopt the open source UI libraries, if possible. In the React.js land, I used a bit of Charkra UI and Reakit.

I'm currently considering React-aria, HeadlessUI, Radix-ui and Reakit for reimplementing the user-interface for a customer, but i find it hard to choose.

I’ve got some libraries I’m looking into to fill the gap. Currently looking at radix, reakit, and react-spectrum.

reakit - Toolkit for building accessible rich web apps with React

Reakit is a lower-level component library for building accessible high-level UI libraries, design systems and applications with React. Reakit is tiny and fast.

1. Reakit

Regardless of what you use for styling though, you should look into so-called headless ui components. These are hooks and components only focused on functionality and accessibility, which you then use to build your own styled components. Some examples are https://reakit.io/, https://www.downshift-js.com/ and https://headlessui.dev/.

For common components, I can't recommend Reakit enough. It's a keyboard accessible, unstyled component library with dialogs, popovers, and much more. I use it for all of my personal projects nowadays. Combined with Framer Motion for animation and Styled Components for styling, it's a killer mix.

You may increase the rendering efficiency of tabular and huge list data by using the React Virtualized module. React apps perform better overall when the quantity of requests and DOM elements is limited. React Virtualized is comparable to many other tools; however, what sets it apart from the competition is the sheer volume of features and excellent upkeep.

17.react-virtualized

If you have been using React for awhile, you may have heard of the infamous virtualisation library react-window or it's predecessor react-virtualized

React Virtualized is a React library that helps you work with large lists and tabular data efficiently in React. It has more than 25K stars on GitHub and more than 2.5 million weekly downloads on NPM as of August 2023.

Use virtualization (e.g. react-virtualized) to prevent off-screen components from actually rendering.

Virtualization can be achieved using third-party libraries like react-window or react-virtualized. These libraries provide a way to render only the visible data and load more data as needed, resulting in faster application performance.

You can implement the same pattern on the web when dealing with large amount of data. There are some libraries for React that trivialize this, like https://github.com/bvaughn/react-virtualized

Oh, right. I totally forgot to mention that– but the idea of "less rendering" in this case seems less like a Suspense concern and more like a windowing concern. I've written a few libraries for that stuff (react-window and react-virtualized) although there are others that may fit your needs better. Their main focus is limiting what you're rendering to more or less only what's on the screen at any given point. Combine that with memoized filtering and I would imagine you're set.

I've used the InfiniteLoader from react-virtualized in combination with useInfiniteQuery from @tanstack/react-query and it was relatively painless.

Here’s a react library https://github.com/bvaughn/react-virtualized