My understanding was that the developers plan was to develop JupyterLab as a future version of Jupyter Notebook. But it seems that both of them now get updates. My question is what is: When to use JupyterLab or Jupyter Notebook and waht is the difference between them?
Jupyter Notebook 7
91–100 of 118 posts
Re: Jupyter Notebook 7
#92Man Open Source software should not post announcements like this using a blogging platform that nags you to pay to view posts. Like it's possible to dismiss the prompt and view the post (for now at least) but something about that definitely feels off.
Getting paid feels off?
Does medium pay enough for that to be worthwhile?
Re: Jupyter Notebook 7
#93Earlier quoted context omitted.
You mean the tiny little 20px banner at the top? Hardly an issue IMO. Medium has a pretty sustainable, but different than most blogging platforms, business model.
No, the 50% of my whole window overlay from the bottom.
I'm logged in, that might be why I don't see it. That's obnoxious.
Re: Jupyter Notebook 7
#94Man Open Source software should not post announcements like this using a blogging platform that nags you to pay to view posts. Like it's possible to dismiss the prompt and view the post (for now at least) but something about that definitely feels off.
Getting paid feels off?
I don't have a great view of how the organization behind Jupyter operates, but I'd be really surprised if they went with Medium as a way to support themselves. What feels off is an open source project (likely by accident or unwittingly) steering users towards giving to a for-profit company.
Re: Jupyter Notebook 7
#95I have never understood the appeal of this. You can generate good looking presentations, but that is all. Is any real science done with this or is it the Powerpoint for PyCon talks?
Like everything else in the Python ecosystem, it's half-baked and not composable. People use it for two reasons: a) because they need to get those graphs on the screen and this is the only way b) running ML code on a remote, beefier server.
>People use it for two reasons: a) because they need to get those graphs on the screen and this is the only way b) running ML code on a remote, beefier server.
Do you have a source of this, or is it something you dreamed up? Weird claim as none of those are my use case.
Re: Jupyter Notebook 7
#96Man Open Source software should not post announcements like this using a blogging platform that nags you to pay to view posts. Like it's possible to dismiss the prompt and view the post (for now at least) but something about that definitely feels off.
I don't share the popular anti-Medium sentiment. For many occasional bloggers, it makes sense; otherwise, they would post in the walled gardens of Facebook and LinkedIn, as thread-monsters on Twitter, or - not at all. Still, for a large open-source project, there is no overhead in using a static site generator. And plenty of benefits. The good news is that moving your stuff from Medium to such is easy. Up to you if y…
I don't hate Medium, it just feels out of place here.
Re: Jupyter Notebook 7
#97Earlier quoted context omitted.
I've long switched to Emacs/Org, but used JupyterLab extensively before (as a data scientist). It's way more powerful than vanilla notebooks since you can open notebooks/code/related side-by-side, easier to extend (with lab extensions), etc. I always thought people only still used vanilla notebooks because that's what people say they use, e.g. "I work with Jupyter notebooks" (even though that may well be in JupyterLa…
I have used org-mode/babel as a notebook replacement, and obviously the flexibility and the editing capabilities are vastly superior to Jupyter notebook, but I fund it sluggish. I assume that, at least in my setup (using babel-python), the kernel is invoked synchronously. I also didn't try to get any form of completion working, but it should be possible and it would be nice to have. What is your setup?
There is ob-async that worked well back when I tried it. Might be worth a look if the synchronous nature of the executions is slowing you down.
Re: Jupyter Notebook 7
#98I have never understood the appeal of this. You can generate good looking presentations, but that is all. Is any real science done with this or is it the Powerpoint for PyCon talks?
I didn‘t „get“ Jupyter the first time it used it. A year later it clicked. A Notebook keeps state while you write it. This is different from IDEs, where programs lose state while you are writing code. Now I use it all the time - next to an open IDE, as a playground to quickly test ideas and algorithms.
IDEs can 100% do this, too. The art of connecting to a running program using the debugger is just something folks stopped caring about.
This led a lot of programming environments to where batch loading of the code is basically required. But "image based" workflows are a very old concept and work great with practice. Some older languages were based on this idea. (Smalltalk being the main one that pushed this way. Common Lisp also has good support for interacting with the running system.)
It is a shame, as many folks assume everything has to be "repl" driven, when that is only a part of what made image based workflows work.
Re: Jupyter Notebook 7
#99I am curious how do you use Jupyter? For me, it used to be Jupyter Notebook. For reasons I cannot pinpoint, I never got convinced to JupyterLab. Sometimes I use Google Colab, primarily for sharing and using GPU for deep learning. Now, when I run it locally, I do it in Visual Studio Code ( https://code.visualstudio.com/docs/datascience/jupyter-noteb... ), since I don't need to jump back and forth between it and the re…
The vscode version, for me, has tended to be a better experience, with fewer random disappointments [0], than the pycharm version. Which is a shame, because the pycharm version, if it got at least as good as pycharm generally, would probably be better imo. But I hear that the new jetbrains notebook ide is the one getting the love
[0]:
- random unusable scrolling with vim mode
- gg scrolls to top of notebook rather than top of cell
- seemingly more-limited refactoring
- ipykernel headaches when I’ve already specified the project interpreter
- randomly cell contents get erased on cell execution
- wsl headaches (allowing firewall exceptions for each new project)
- windows jupyter headaches (having to manually terminate jupyter sometimes to quit the ide)
- sometimes the debugger gets stuck fetching variables before displaying them
- some kind of incompatibility between non-pycharm-created notebooks possibly related to nb format version so they can’t be read
- removal of (ui affordances for?) the cell mode for scripts?
Re: Jupyter Notebook 7
#100Earlier quoted context omitted.
The point here is that they've unified the codebases. The application "Jupyter Notebook" is just a single-document version of "JupyterLab", designed to just do that one part of Lab. Previously there was "Jupyter Notebook". Then they separately wrote JupyterLab (creating a brand new implementation of notebooks for it). Now, they're taken the JupyterLab notebook code and used it to replace "Jupyter Notebook".
Does it mean that RISE https://rise.readthedocs.io/en/stable/ will break? I use it sometimes to turn a notebook into a presentation and it doesn’t work with Jupyter Labs
You should check out https://github.com/deathbeds/jupyterlab-deck