[dead]
Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
51–60 of 100 posts
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#52Honest question: what is not modern about JupyterLab? I know JupyterLab has existed for a long time, but continuous development has kept it modern.
The need to start the server is really annoying. Especially when you have notebooks in multiple places, or multiple virtual envs. This is why I moved to working with Jupyter notebooks in VS Code, there is no server to manually start.
Vscode will start the server for you, in practice. This is great if you just want to get going. It gives you a bit less flexibility though, if you want to do something fancy.
Vscode can also connect to existing servers. This can be very useful. For instance, you can put a ton of data and CPU in a server and work with vscode on a small laptop. If network latency is low enough, this works great.
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#53I am the author of Zasper. The unique feature of Zasper is that the Jupyter kernel handling is built with Go coroutines and is far superior to how it's done by JupyterLab in Python. Zasper uses one fourth of RAM and one fourth of CPU used by Jupterlab. While Jupyterlab uses around 104.8 MB of RAM and 0.8 CPUs, Zasper uses 26.7 MB of RAM and 0.2 CPUs. Other features like Search are slow because they are not refined. I…
How was your experience working with 0mq?
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#54Earlier quoted context omitted.
> JupyterLab kernel There is no such thing. There are Jupyter kernels. JupyterLab is just one of many UIs that speak the Jupyter protocol. Other examples include the original Jupyter notebook editor, VSCode Jupyter extension, and now Zasper. I'm pretty sure Sage was always intended as a project that integrates the world, never "small footprint".
>> JupyterLab kernel > There is no such thing. A Web search reveals that the alternate term "Jupyter kernel," appears equally often. The terms are interchangeable. > I'm pretty sure Sage was always intended as a project that integrates the world, never "small footprint". A large install became true eventually, but it began as a small Python-based install, about 120 KB. Then people asked for extensions, and William St…
No.
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#55Earlier quoted context omitted.
That's stellar sportmanship right there. Not that jupyter's team needed even more respect from the community but damn.
I think that's fairly normal, having alternative frontends can only be beneficial to the community. I know it also look like there is a single Jupyter team, but the project is quite large, there are a lot of constraints and disagreements internally and there is not way to accomodate all users in the default jupyter install. Alternative are always welcome ; at least if they don't fragment the ecosystem by being not ba…
> Alternative are always welcome; at least if they don't fragment the ecosystem by being not backward compatible with the default.
Genuinely curious; what mechanisms has Jupyter introduced to prevent ecosystem fragmentation?
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#56I am the author of Zasper. The unique feature of Zasper is that the Jupyter kernel handling is built with Go coroutines and is far superior to how it's done by JupyterLab in Python. Zasper uses one fourth of RAM and one fourth of CPU used by Jupterlab. While Jupyterlab uses around 104.8 MB of RAM and 0.8 CPUs, Zasper uses 26.7 MB of RAM and 0.2 CPUs. Other features like Search are slow because they are not refined. I…
IPython maintainer and Jupyter dev (even if I barely touch frontend stuff these days). Happy to see diversity, keep up the good work and happy new year. Feel free to open issues upstream if you find lack of documentation or issue with protocol. You can also try to reach to jupyter media strategy team, maybe they'll be open to have a blog post about this on blog.jupyter.org
I’m not adding a lot to the conversation, but it’s not often you run into someone who contributes to creating a tool so fundamental to your daily life, career, growth as a researcher etc, so let me just take the opportunity to say: thank you and the rest of your team for creating such an amazing interactive tool.
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#57It's probably an unrelated post (apologies in advance) but I wanted to shoutout to the Marimo ( https://marimo.io ), it's the only Jupyter alternative that really got me excited, it's like Streamlit and Jupyter had a kid (and the kid took the best genes from both).
>> marimo notebooks are pure Python and stored as .py files That sounds like a solid improvement. I’m going to give this a test drive. I feel like modularity is one of the hardest aspects of Jupyter notebooks in a team environment. I’d be interested to hear if anyone has cracked a workflow with notebooks for larger teams. Notebooks are easy for solo or very small teams, and the literate programming style benefits sti…
I actually think the problem you are describing is actually sometimes helpful from a design perspective, if you can be conscientious enough to periodically review your notebooks and figure out what is the actual useful code which should be properly integrated into the codebase vs what is the “one-off” / non-modular code. Like you mentioned, calculation vs side-effects is one way to help you decide but not the only. There’s definitely no single answer. The key is to just periodically figure out what ought to be refactored into library code, which notebooks should just be straight up deleted (hopefully as many as possible - you can always get them back in your git history if needed!), and so on.
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#58Earlier quoted context omitted.
Have you tried the Jupyter desktop app? It's more self-contained.
Yes, I tried Jupyter Desktop. It is fantastic, I like that you can double click on notebook file to open app. However, it might be a little to complicated for beginners, you need to setup Python and select kernels. That's too much.
People can program in python but cannot select a kernel from a list? I find that hard to believe
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#59Good looking project I will check this out for sure
Re: Zasper: A Modern and Efficient Alternative to JupyterLab, Built in Go
#60Can I disconnect and reconnect from a running frontend (close and reopen a tab) and not lose any output?