dash

This account was spamming Python repositories with the same type of low value obvious backdoor spam.[1] Full list of attempted pull requests (all deleted seemingly by GitHub): 1 https://www.github.com/KurtBestor/Hitomi-Downloader/pull/7638 2 https://www.github.com/home-assistant/core/pull/130423 3 https://www.github.com/celery/celery/pull/9407 4 https://www.github.com/chriskiehl/Gooey/pull/921 5 https://www.github.com/crewAIInc/crewAI/pull/1582 6 https://www.github.com/cumulo-autumn/StreamDiffusion/pull/177 7 https://www.github.com/AUTOMATIC1111/stable-diffusion-webui/pull/16646 8 https://www.github.com/Aider-AI/aider/pull/2343 9 https://www.github.com/aboul3la/Sublist3r/pull/383 10 https://www.github.com/plotly/dash/pull/3073 11 https://www.github.com/soimort/you-get/pull/3034 12 https://www.github.com/streamlink/

Isn't this what Dash[1] does? You can see a very similar graph in the built-in debugging tools. [1] https://github.com/plotly/dash

I created something like this inside a tech giant once. It never saw the light of day with regard to usership. It's good to see someone doing the same in the open source world. A brief summary of what I did: * Python-powered apps, like this * React was used to handle lifecycle. Basically, I avoided writing any kind of lifecycle management because I just wanted to do exactly what React would do. This was achieved via events firing when React lifecycle events fired. If props changed on the server, I'd send the new props to React to see if it would trigger a lifecycle event. If a lifecycle event was triggered, I'd replicate it onto the server which could again render new props. * The result was a nice seamless support for both native React components and the newfangled Python components (which could be made up of either more React components

Useful list. Dash & bokeh as two more in the space https://github.com/plotly/dash https://docs.bokeh.org/en/latest/

Why do you have to learn JS? If you just want to make a web app and add some interactive 3D models on it, there're some Python libraries can help with that, like: https://github.com/streamlit/streamlit https://github.com/wang0618/PyWebIO https://github.com/plotly/dash

Hello HN! Nice to see this up here. Chris here, cofounder of Plotly. Falcon is open source and works without an internet connection or a Plotly Chart Studio account. Falcon wires together our graphing library plotly.js (https://github.com/plotly/plotly.js/), the plotly.js chart editor (https://github.com/plotly/react-chart-editor), Electron, and some open source NPM packages for connecting to databases. Just FYI - As a company (Plotly), we're spending most of our development effort these days on Dash Open Source (https://github.com/plotly/dash) and Dash Enterprise (https://plotly.com/dash). Truth be told, we found that most companies we worked with preferred to own the analytical backend. We also heard many stories of organizations running into roadblocks with off-the-shelf SQL or BI tools (Falcon included!). Our approach with Dash is to

We built Sourcegraph, which is a web-based code search and navigation tool. Our Python support is in beta, and you can try it out at https://sourcegraph.com/github.com/plotly/dash/-/blob/dash/d.... (And hit Alt+D/Opt+D to search by symbol.) Sourcegraph also supports a bunch of other languages: https://sourcegraph.com/help/languages. It gives you nice URLs (hit Alt+Y/Opt+Y to get the full commit ID in the URL to make it permanent). Would love to hear your feedback.