> written in Rust > XY is an extremely fast, interactive, customizable Python charting library which is it?
Its a Python library with some rust in it, to speed up some of the calculations
Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
11–20 of 50 posts
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#12> XY is an extremely fast, interactive, customizable Python charting library for the web
I have adjusted the title
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#13> written in Rust > XY is an extremely fast, interactive, customizable Python charting library which is it?
Python libraries can have compiled artifacts that were written in any language. This is such a library.
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#14I’m not convinced GPU acceleration is a meaningful advantage for most charting use cases. Most dashboards don’t render enough data for it to matter. Once a chart is dense enough for rendering to become the bottleneck, it normally is already be too crowded to be meaningful. Zooming can justify supporting larger datasets, but sampling/viewport culling and level of detail often avoid drawing unnecessary points...
There are some niche charting applications which are offloaded to FPGAs and even ASICs.
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#15I misread it as ‘Chatting’ library and I was so confused on the GitHub page.
Love rust as the impl.
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#16it's possible to render data out-of-core with XY, allowing it to render the entirety of OpenStreetMaps (that's 10,742,674,832 nodes!) with sub-second pan/zooms. it's a bit difficult to host online but you can try it out locally: https://github.com/reflex-dev/xy/tree/main/examples/osm
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#17I’m not convinced GPU acceleration is a meaningful advantage for most charting use cases. Most dashboards don’t render enough data for it to matter. Once a chart is dense enough for rendering to become the bottleneck, it normally is already be too crowded to be meaningful. Zooming can justify supporting larger datasets, but sampling/viewport culling and level of detail often avoid drawing unnecessary points...
I constantly have to work around the slowness of matplotlib when creating animated sequences for my scientific work (even with the Agg back end)
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#18absolutely fantastic.
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#19super cool!
Re: Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library
#20I’m not convinced GPU acceleration is a meaningful advantage for most charting use cases. Most dashboards don’t render enough data for it to matter. Once a chart is dense enough for rendering to become the bottleneck, it normally is already be too crowded to be meaningful. Zooming can justify supporting larger datasets, but sampling/viewport culling and level of detail often avoid drawing unnecessary points...
I constantly have to work around the slowness of matplotlib when creating animated sequences for my scientific work (even with the Agg back end)
How many points are you working with usually?