olifolkerd

The latest 4.8 release comes with a load of great new features including a Horizontal virtual DOM for handling tables with large numbers of column, RTL language support and ESM Module importing.

That feature will be coming soon :)

Thanks.

By removing the need for 3rd party dependencies it helps reduce the overall size of the package, made it easier to manage the source of the system, made it easier for developers to import and dramatically increased the performance of the table, Tabulator used to be built on jQuery but that was a beast of a library and eventually became a bottle neck harming performance more than it aided development.

Removing the need for dependencies was also a great learning experience to implement a variety of systems that you would usually go straight to another library for.

When there is something bespoke in one of the extensible modules there are the occasional use of library's, such as the xlsx downloader or the sparkline formatter. but i only use these in optional components and keep the core dependency free :)

Thanks. I deliberately avoided 3rd party dependencies to try and make the code base as small as possible.

I use react native wrappers at work and embed webviews that allow components like these to be used.

That being said, having a react-native variant for this is on the long term road map

All features of Tabulator are free including a lot of features AG Grid charges for for commercial licenses

Tabulator is licensed under MIT so is free for all to use, even on commercial projects.

You can can do this but for large data sets it would take ages and doesnt over come the main issue.

Lets say we are working with 10,000 rows

Yes loading that many elements into the DOM is slow and your approach would stop it blocking, however what it dosnt do is stop the sheer number of elements from overloading the DOM.

Most browsers simply cant handle that many elements in the DOM, if you try and scroll a div containing that may elements at best it will be sluggish and at worst it will simply crash the browser. on devices without much memory it is very likely that the whole DOM will freeze up and make the site unusable.

By adding and deleting the elements as they become visible/hidden it keeps the number of elements in the DOM to a minimum, while improving load time and adding only a bit of extra processing to the scroll event, which modern browsers can handle with ease. giving all round the best solution