Show HN: Persistent Jupyter kernel execution and live output streaming in VSCode

Show HN: Persistent Jupyter kernel execution and live output streaming in VSCode(github.com)

7 points by rnoro_ 4 days ago | 3 comments

Hi HN, Every time I ran a training loop for a few days via Jupyter Notebook and ran into issues (network disconnected, my laptop suddenly died, etc.), I suffered from losing my ipykernel and cell outputs. I wanted to keep seeing my live outputs right inside the IDE without constantly checking W&B or log files. It is such a hassle. That's why I built Tithon. Let me know what you think!

nater5000 3 days ago |

Nah, this is working backwards. I've seen this dynamic plenty of times before: someone gets comfortable with some workflow in a limited context, and try to force into larger, more sophisticated context where it doesn't work as well rather than accepting that there are better tools for the job.

Nothing wrong with putting this stuff out there I guess, but if anybody I was working with was doing anything like this, we'd be scheduling a few sit-downs where I explain the proper way of handling this stuff and spare them the headaches of trying to fit a square peg into a round hole.

singular_atomic 4 days ago |

This is really really useful and something I've been looking to build in the roadmap for my notebook IDE (https://trykrypton.com/)

Any reason why you also decided to go with .py files as part of your detachable kernel architecture?

rnoro_ 3 days ago | |

Thanks! I wanted to drop the dependency on .ipynb for this version, so I went with .py files instead. The detachable kernel itself isn't tied to .py, so I'm considering a dedicated extension like .pynb (Python notebook) to distinguish notebooks from regular Python scripts in the future.