Live data from Hacker News

JupyterLab: the next generation of the Jupyter Notebook

blog.jupyter.org

111–119 of 119 posts

Re: JupyterLab: the next generation of the Jupyter Notebook

#111

What is the advantage of the graphical console vs. the notebook? I don't get (yet) why I would need the console when I have the notebook.

One thing people use it for is ephemeral computations that they don't need/want to be saved, so they don't want to bother with dealing with a notebook file.

Another thing we could support in the future is easily switching kernels mid-stream in the console. Maybe that makes sense---it did come up in conversation yesterday night here at scipy.

Re: JupyterLab: the next generation of the Jupyter Notebook

#113
post #49
post #5

> JupyterLab adapts easily to multiple workflow needs, letting you move from a Notebook/narrative focus to a script/console one. I'm not sure I like where that design is going. It's starting to look an awful lot like RStudio and Matlab and I moved away from those tools for a reason. My favourite thing about Jupyter is that it is focused on notebooks and narrative. It brought about a revolution of sorts; now we have p…

Context: We use Jupyter heavily (mostly against Spark). In my experience there is a set of things that "traditional" Jupyter notebooks does really well. Anytime you have a linear flow of steps the notebook metaphor works really well. However, if you are doing things approaching traditional development, where you have multiple sources of data, or loops that require debugging, or basically anything that isn't linear in…

Jupyter really is just for analysis. I prefer standard IDEs like Jetbrains for application development.

Re: JupyterLab: the next generation of the Jupyter Notebook

#116
post #53

Earlier quoted context omitted.

Ditto! Amazing. Seems the inverse of notebooks where it is a notebook with predominantly text and a box with code and results. I'm going to take Hydrogen for a spin. I still rely heavily on Mathematica, since the notebook interface won me over years and years ago. I think the next Mathematica paradigm to be redone in JupyterLab is easy connections to data without all the connection string fuss. You can just put in so…

I found Jupyter notebooks more stable than Mathematica.

In what sense? I only get glitches in Mathematica when I am hitting extremely huge curated data from Wolfram and trying to do something at the same time. I have only used Jupyter notebooks for a page or two, and mostly toy problems, so I can't say I have stress tested them. I do like Hydrogen, though.

Re: JupyterLab: the next generation of the Jupyter Notebook

#117
post #41

Earlier quoted context omitted.

But from what I can tell, it still doesn't look integrated. It looks like separate tools all glued on the same webpage. Now I have yet a separate terminal, a separate file manager, a separate Python REPL, ... How is this any better than just keeping those applications open and switching between them? I really hope this isn't just a poorly-implemented window manager inside a web browser.

For some plugins integration just means visual integration (i.e. window-manager integration). And, to be clear, this one is not poorly-implemented. It's based on a very powerful web-application toolkit called PhosphorJS written by very experienced UI developers. For other plugins there is very nice integration so that you can have interactions in one plugin update outputs in another and vice-versa. The ease of creati…

I would want integration into my existing workflow, not integration that replaces my workflow with something completely different.

For me, this means using emacs-ipython-notebook. This brings the ability to interact with a running IPython Kernel into the text editor that I use daily. It's the best of both worlds: interactive plotting+notebooks+rapid development assistance from IPython, and thanks to Emacs, all the keybindings are what I expect and I'm already familiar with how to extend the environment to suit my needs. EIN has been transformative for me.

Perhaps my needs don't match the needs of others. For most people, I imagine the Jupyter-lab style of environment that's self-contained in a browser would in fact be a step up from the ad-hoc notepad++ windows and PuTTY sessions used previously.

Re: JupyterLab: the next generation of the Jupyter Notebook

#118
post #87

Earlier quoted context omitted.

Seeing as you're heavily using Spark, have you had a look at Apache Zeppelin (site: https://zeppelin.apache.org , demo: https://www.youtube.com/watch?v=J6Ei1RMG5Xo )? Seems like a more powerful notebook approach, plus better architecture for using embedded d3.js viz. Also painless templated SQL -> published dashboard looks great for getting data visible early on.

Yes. Not really a fan. It looks nice, but the installation experience is (was?) terrible (as in - didn't work at all). Note the long gap between the 0.5.6 release (January) and the 0.6.0 release (July)? There were 3 (4?) Spark releases in that time, and that meant that none of the out-of-the-box released worked for anything except the version of Spark you downloaded with it (and from memory that had problems too) I g…

One of the Apache Zeppelin committers here.

Thanks for honest feedback (although it sounds bitter) - we are working hard on improving situation with release schedule indeed.

If there is any chance you could elaborate on installation experience though a JIRA issue [1] - that would be very much appreciated.

1. https://issues.apache.org/jira/browse/ZEPPELIN

Re: JupyterLab: the next generation of the Jupyter Notebook

#119
post #82

Earlier quoted context omitted.

true but the languages are siloed, each notebook runs just one language. with beaker the languages can communicate with each other. there's no easier way to combine python and javascript for d3, for example: https://pub.beakernotebook.com/publications/7fdcaaa6-fb83-11... there are lot more differences in the UI as well.

Not everyone needs more than one language in the same notebook communicating between each other. But if required, then the cell magic system looks superior to me: have a look at %%fortran, %%cython, %%javascript, %%html, %%bash options. Also it is possible to switch kernels in the same notebook, but serialization of state between kernels is handled by user.

Cell magics just seem like one possible method of choosing which language to use, a menu such as what beaker uses seems alright too. I was setting up cling (the C++ kernel) today and I gave up at realising that the interpreter is spun up in a subprocess, rather than a kernel persisted across cells. Without cross cell support, mixing languages is a limited feature of jupyter.
Post reply on HN