dtale VS perspective

[D-Tale](https://github.com/man-group/dtale) has recently released version 3.2.0 on pypi & conda-forge: ``` pip install -U dtale conda install dtale -c conda-forge ``` But if you want to take it one step further you can now integrate it with [ArcticDB](https://github.com/man-group/ArcticDB): ``` pip install -U dtale[arcticdb] ``` This allows you the ability to navigate your libraries of datasets saved to your ArcticDB database! But the best part is that all the reads are occuring directly against ArcticDB so some of the memory constraints you may have been hit with before are now a thing of the past. Here's a full write up how to use this functionality along with a quick demo: https://github.com/man-group/dtale/blob/master/docs/arcticdb/ARCTICDB\_INTEGRATION.md Hope this helps & please support open-source by throwing your star on the [repo](https://github.com/man-group/dtale). Thanks! 🙏

I've looked into external tooling, libs such as dtale, which feel overly complicated for my use case (but I'm open to alternatives). What I would like to have instead is something akin to Spyder's variable viewer, which allows sorting by column. VSCode goes a step further and also provides the ability to filter the dataframe.

D-Tale: A Python library that provides an interactive web-based interface for data exploration and analysis.

Try this: https://github.com/man-group/dtale

https://github.com/man-group/dtale

I find that I'm actually a lot faster using basic Pandas methods to get the data I want in exactly the form I want it.

If I really want to show everything, I just use:

'''

Just added "Time Series Analysis" in v1.60.1 of D-Tale on pypi & conda-forge: pip install -U dtale conda install dtale -c conda-forge This feature provides a quick and easy way to visualize the usage of the following time series analysis function in statsmodels:

Your data is stored in memory so the size of your dataframe is limited to the memory of your machine. That being said we’ve allowed users to swap out the machanism which stores the data so you can use something like Redis or Shelve to allieviate memory. Here’s some documentation: https://github.com/man-group/dtale/blob/master/docs/GLOBAL_STATE.md

Why do you want to render to canvas?

Perspective seems to be the most performant html table. It is more focused on extremely fast updates than styling, although it looks good.

Glide is a newcomer that also renders to canvas.

https://github.com/finos/perspective

https://github.com/glideapps/glide-data-grid

SQL workbench also uses https://perspective.finos.org/ for tables. It's a WASM table library which pairs nicely with duckdb and works well with large tables.

Yes. We are working on adding support for aggregation and pivoting using https://github.com/finos/perspective

I haven't looked extensively at react-datasheet. It looks like it is trying to build more of a full product than the other data tables.

I have used ag-grid extensively, its an impressive product. Some pieces are a little awkward to use, particularly auto-sizing. But generally ag-grid has thought of most functionality and has a solution. The creator of ag-grid had a great interview on Javascript Jabber [1].

The other serious data table component that I have seen is FinOS Perspective [2]. This is extremely high performance, also more specialized and probably harder to customize. I think Perspective renders to a canvas element from Rust/C++ compiled to WASM (not 100% sure). It is also made for streaming updates.

AG-Grid supports streaming updates... but only in the commercial version.

Eventually the data model for these types of tables becomes tricky. I will be investigating parquet-wasm for my use case. Hit me up if you want to collaborate.

[1] https://blog.ag-grid.com/javascript-jabber-podcast/

[2] https://perspective.finos.org/

Something like https://github.com/finos/perspective ? We use an OLAP(-y) WASM engine to provide query-ability to our data visualization tool, and doing the calculations in the browser is cheaper and simpler than a server-side database for datasets that fit in browser memory.