comlink VS react-window

Feels like taking a general Comlink-like system & making it more component oriented. Good ideas. https://github.com/GoogleChromeLabs/comlink

React UI Framework: https://ant.design/ Reactive: https://www.learnrxjs.io/ Workers: https://github.com/GoogleChromeLabs/comlink Graphics: https://www.pixijs.com/

Reminds me of Comlink

Now that we have a way to create PDF files, we can create a web worker to run the renderPDF function in a separate thread. Here’s an example of a web worker that uses comlink to expose the renderPDF function as an asynchronous function:

To streamline the process of configuring the Service Worker and simplify communication between the app and the Service Worker, we will be using the comlink library.

While there's no realistic way to provide a security boundary between JavaScript modules, Workers are a possibility [1].

The code with the more restricted set of permissions must run in the Worker. That code then communicates with the rest of your app through postMessage / SharedArrayBuffer, perhaps using ComLink [2].

[1] https://deno.land/[email protected]/runtime/workers#specifying-...

[2] https://github.com/GoogleChromeLabs/comlink

The worker API is very simple, you would post a message to the worker. The worker would have the code to process and reply back with the results to the listeners. To make it even easier Google has created the comlink library.

As we have seen in the previous section we can implement virtual scrolling from scratch. In this section, we'll discuss a third-party tool called react-window that allows us to implement virtual scrolling in a much easier way.

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 Window is used to render long lists. Imagine you have a list of 1,000 items. Only ten are visible simultaneously, but your code tries to render all 1,000 items simultaneously.

You can try react-window by Brian Vaughn

I'm trying to use react-window and react-nice-scroll together but unfortunately it didn't work at all. As soon as I wrap my component with from react-nice-scroll everything disappears.

This is what you should look into. (Virtualization)

Take a look at react-window. But just my perspective; if you haven't needed to look into what virtualization is, it's probably because you haven't had a need for it yet. The one implication (which you'll see in another comment form me in this thread) is that it removes CTRL+F search functionality for items outside of the "window".

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.

If the API data is not paginated (i.e. you’re getting all your data in one go), then you may not need pagination. If rendering performance is an issue, a virtualized list may be more appropriate. If the response is too big and is slow to fetch it’s another issue entirely, since if the API doesn’t support offsets / pages you would need to invent a criteria to paginate your data on, or fetch it on the server using React Server Components which gives you implement a cache layer and potentially allows to only send a chunk of that data to the client, but you see how that can get complex fast.

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.