4 ms·
> Dash: Enterprise-grade, one-framework-fits all solution. Unlimitied design flexibility & great scalability. This is hilarious because the official documentat
by curiousgal 6y ago
> Dash: Enterprise-grade, one-framework-fits all solution. Unlimitied design flexibility & great scalability.
This is hilarious because the official documentation[0] suggests that you use hidden divs to store data as json if you need to share it between callbacks (which is more common than they would have you believe). And good luck serializing data structures with complex types in them.
Python frameworks are all fun and dandy untill you look under the hood or try to push the envelope.
Personally for all my dashboard needs I have found R's Shiny to be the best.
0. https://dash.plotly.com/sharing-data-between-callbacks https://dash.plotly.com/sharing-data-between-callbacks
- nicolaskruchten 6y agoYeah we need to update that page: there is a replacement called the Store component that uses local storage or non-DOM memory now. https://dash.plotly.com/dash-core-components/store https://dash.plotly.com/dash-core-components/store
- oblvious-earth 6y agoThis is a documentation issue not a framework issue. For a long time you do client side storing of data with dcc.Store: https://dash.plotly.com/dash-core-components/store https://dash.plotly.com/dash-core-components/store For server side storing of data you should use a simple DB store like Redis. Dash has really matured in the last 2 years and you can actually push the envelope in a lot of places now without having to do incredibly hacky things. The documentation though still isn't great...
- nicolaskruchten 6y agoWe've finally (!) gotten around to updating this page, thanks to your gentle nudge ;)