21–30 of 44 posts
Accidentally closing a browser tab seems like it would end the session and wipe out my whole Jupyter session, variables and all.
I didn't read very deeply, but I was surprised to see something like a Jupyter notebook mentioned as a use-case. The marketing pitch seems to suggest that these hosted sessions are relatively stateless, so I'd hesitate to trust an interactive Jupyter session with one. Accidentally closing a browser tab seems like it would end the session and wipe out my whole Jupyter session, variables and all.
When backends are spawned, there is a period of time that they remain alive without a connection. By default, it's 5 minutes. So if you accidentally close a tab, but open it back within 5 minutes, the kernel is still there.
This looks really interesting, and something that could solve a semi-immediate pain point but I can’t find any data on the production plan other than the price. Is that information available anywhere?
With the production plan we increase the memory limit of the backends to 2GB, up the number of concurrent backends to 20 (it's a soft limit), up the limit on backend runtime to 24h, and have images eagerly pushed rather than lazily pulled for faster start times. If you're open to chatting about your use case, feel free to reach out to the email on my HN profile.
I didn't read very deeply, but I was surprised to see something like a Jupyter notebook mentioned as a use-case. The marketing pitch seems to suggest that these hosted sessions are relatively stateless, so I'd hesitate to trust an interactive Jupyter session with one. Accidentally closing a browser tab seems like it would end the session and wipe out my whole Jupyter session, variables and all.
The use case in that example is for ephemeral notebooks used for demos. It's also good for running notebooks for temporary classroom use. When backends are spawned, there is a period of time that they remain alive without a connection. By default, it's 5 minutes. So if you accidentally close a tab, but open it back within 5 minutes, the kernel is still there.
I've seen a lot of bad engineering go into solving that problem, this seems like a better way.
Another reinvention of Erlang processes?
Sometimes I explain it to Erlang/Elixir world people as “GenServer-as-a-service”.
Hey HN! I'm a co-founder of Jamsocket, happy to answer any questions. We've previously been on HN for Plane, which is the open-source engine behind Jamsocket. https://news.ycombinator.com/item?id=33178797 Sorry for the website performance issues, I've disabled the animation which should help.
Hey HN! I'm a co-founder of Jamsocket, happy to answer any questions. We've previously been on HN for Plane, which is the open-source engine behind Jamsocket. https://news.ycombinator.com/item?id=33178797 Sorry for the website performance issues, I've disabled the animation which should help.
Do you support WebTransport in addition to WebSockets?
Hey HN! I'm a co-founder of Jamsocket, happy to answer any questions. We've previously been on HN for Plane, which is the open-source engine behind Jamsocket. https://news.ycombinator.com/item?id=33178797 Sorry for the website performance issues, I've disabled the animation which should help.