react-vis VS ag-Grid

Install react-vis by using the following command:

I've heard good things about Uber's react-vis https://www.npmjs.com/package/react-vis

D3.js is great for custom data viz. You can get started by including the library in a script tag and not have to mess around with a bundler like Webpack until you are ready and just use plane CSS. D3.js doesn't work well with JS frameworks like React - it was jQuery like DOM manipulation functions. I find the best approach is to let D3 manage its chart and leave React for the UI. Or you can use a more React friendly library like React Viz from Uber. While D3 is great for custom data viz it's time consuming for standard charts. There are a lot of charting libraries out there like Chart.js. There is also Plot which is built on D3.js.

React Vis averages 100,000+ weekly downloads, 8.3k stars and 850 forks on Github.

react-vis

I am trying to use react-vis library in my project. In their readme file, they have asked to import library by adding following lines in non-node environment:

I had an existing working react code written in Typescript (and hence ES6) using react-vis library. The library itself seem to use ES6.

I have referenced react-vis library form unpkg as stated in their github repo:

The repository can be found here and is definitely worth taking a look.

react-vis - Data visualization library based on React and d3.

In this post I’ll show you how, using the AG Grid component and Ably Spaces, you can create a React application that allows users to see not only who else is currently viewing the grid, but using a Flowbite Avatar Stack component, what row each user currently has selected.

something like ag-grid? https://github.com/ag-grid/ag-grid

I personally use https://www.ag-grid.com/ for all my data grid needs. It has a free community version (that should get you covered imo) as well as a paid one with advanced features.

To be fair, in any GUI toolkit, the "table" is abolutely the most complex general purpose widget. People really under estimate the difficult of an efficient implementation. Qt spents YEARS improving their QTableWidget class. The implementation is mind-bogglingly complex. I am sure many very smart summer interns (PhDs!) have tried to tweak that class to squeeze every bit of performance possible. The table class in GTK+ and MSFT DotNet's WPF are equally, freakishly insane.

Consider this idea: Most people who use a table class in a GUI framework assume it is essentially infinitely scalable (myself included!). I am talking about millions of rows or thousands of columns with all kinds of silly widgets injected into individual cells. It is a crazy hard computer science problem to solve. I would not doubt there are many PhD thesises written on the topic of fast, scalable table widgets.

Beyond desktop GUI toolkits, people have tried to do the same in a browser (HTML/CSS/JS). Have you seen AG-Grid? Woah, it is unbelievable how much goddamn data you can squeeze into that widget. Most Wall Streets web-based trading apps use it one way or another. It's just so hard to beat. Ref: https://www.ag-grid.com/ There must be 1,000 person years of optimisation sunk into that implementation.