Chart.js VS ag-Grid

ChartsJS for inspiring me with the pie chart.

Most of frontend libraries are made with Vanilla JS. An example of library that you might frequently use is "Chart.js". But React is not compatible with Chart.js so here it comes "React-chartjs-2" A wrapper library to work with Chart.js in React ecosystem. Oh you want to use "three.js" for some cool 3D? you will need "React-three/fiber". In my case, I need to implement "telegram-web-app", not so fast, I have to create my own wrapper to be able to use it.

Chart.js

Chart.js is a free, open-source JavaScript library for data visualization, which supports eight chart types: bar, line, area, pie, bubble, radar, polar and scatter. It's licensed under the permissive MIT license and is renowned for being flexible, lightweight, easy to use and extendible.

They are images so it could be any number of things, datawrapper, charts.js, d3.js to name a few options.

Charts.js for creating diagrams

Connie Leung wrote a tutorial to demonstrate how these new hooks work, integrating an Angular app with the Chart.js library: "DOM reading and writing with new lifecycle hooks in Angular"

Thanks to all who participated in our 2023 Self-Host User Survey! Below is a link to the results, which we've visualized using Chart.js.

Chart.js

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.