react-virtuoso VS solid-docs

If we limit the number of rows rendered to only show the visible items, we can limit the cost of re-rendering the table. Even if there are a large number of rows in the table, only the ones on the screen will be rendered. That can be done by virtualization. I will use react-virtuoso for the app.

react-virtualized is very old and unmaintained. I will plug my fairly popular solution, https://github.com/petyosi/react-virtuoso.

Try virtualization inside your dropdown. For sure it will improve the performance. Check https://virtuoso.dev it's very easy to implement

Shameless plug, I am the author: https://github.com/petyosi/react-virtuoso

I would take a look at React Virtuoso

if it is group chat that many users can write messages into one group means it will be a lot from some point. and suppose there is another list for example user contact list in aside along with chat section, size of dom will grow in app. when user select some contact item react gets sluggish from its rerender aspect. but I don't recommend to start with it unless you are not observe performance issues and app layout is simple to implement this feature there is also https://virtuoso.dev/ for virtualization FYI.

react-virtuoso is a relatively new package for virtualization, published first two years ago. It comes with all the necessary features and support that one might eventually require in a developing project.

So far, react-virtuosso https://virtuoso.dev/ is the only library that supports this.

In many large companies, development becomes slow and incredibly expensive. If an engineer costs 10k a month, the fully burdened cost to the company is often 5-10x that. While the costs increase the output usually goes down. This is something I’ve been thinking about a lot over the last months. As our startup keeps on growing I want to hold on to that startup level of productivity. Petyo just joined as our 100nd team member, so as we reach this initial level of scale this is becoming a more urgent concern.

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Solid.js is a very performant web framework that shares some similarities with React. For example, both use JSX, utilizing the function-based approach to components, but instead of using Virtual DOM, it converts your code to vanilla JS. Still, it is more famous for its approach to fine-grained reactivity by utilizing signals, memos, and effects. Still, the signal is the simplest and most known primitive of Solid. They contain value along with their getter and setter functions, allowing the framework to observe and update the changes as needed in the exact location in the DOM, unlike React, which re-renders the whole component.

Two well-known JavaScript frameworks and libraries used for creating user interfaces are React.js and Solid.js. Solid.js, a lightweight reactive library, prioritizes fine-grained reactivity and efficient rendering through a reactive programming model. However, React.js, which was developed by Facebook, is well known for its declarative architecture based on components and its handling of the virtual DOM (Document Object Model). Different approaches to state management and reactivity set these tools apart, even though they both enable developers to create dynamic and interactive web apps.

Solid.js like Svelte is quite new when compared to React, Angular, and Vue however it might be that pocket Hercules we've all been ignoring because we are so addicted to other frameworks. Solid.js is an interesting framework that deserves to be a part of this discussion. Solid.js pioneered the concept of signals when other Javascript frameworks made reactivity and state management a nightmare for developers, a factor that has contributed to the growth of Solid. Solid.js is incredibly easy to adopt and it aims for a simpler syntax and learning curve compared to other frameworks. It emphasizes the use of pure Javascript functions and avoids concepts like hooks.

React Server Components are the poster child for that trend, but other frameworks such as Solid or Qwik rethink client-server interactions from the ground up.

If you aren't married to the react paradigm, I had a great time with solid.

Frontend : SolidJs.