Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JupyterLab: the next generation of the Jupyter Notebook

blog.jupyter.org

Post reply on HN
Print view View original

11–20 of 119 posts

Re: JupyterLab: the next generation of the Jupyter Notebook

#11

Post by mungoid »

m_ke wrote: post #8
sorenjan wrote: post #6

I love Jupyter notebooks, I just wish I could use them in a dedicated program instead of having to run a server and using a browser based client. It feels hacky and I just prefer native apps for coding and the browser for reading documentation and similar. Even an Electron based program that could be associated with notebook files and hide the server-client model would make it nicer to use. At the moment I like to op…

You should check this https://github.com/nteract/hydrogen/blob/master/README.md out.

Holy cow I never knew that existed! My life could have been so much different the past few months had I known.. I bet I even skimmed past it on HN without even looking.. Shame on me

Re: JupyterLab: the next generation of the Jupyter Notebook

#12

Post by denfromufa »

Jupyter started from ipython, originally mostly written in python and for python. But the project was so successful that it extended for other languages using cell magic and then kernel system. The team is now mostly using JavaScript, Typescript, except for ipython sub-project. Although it's obvious choice for schools, research, analytical work, and publications, still I really wish for more adoption in corporate environment, that got stuck in proprietary tools.

Re: JupyterLab: the next generation of the Jupyter Notebook

#13

Post by rtpg »

sorenjan wrote: post #6

I love Jupyter notebooks, I just wish I could use them in a dedicated program instead of having to run a server and using a browser based client. It feels hacky and I just prefer native apps for coding and the browser for reading documentation and similar. Even an Electron based program that could be associated with notebook files and hide the server-client model would make it nicer to use. At the moment I like to op…

PyCharm has support for python notebooks, but I don't know how well it works with remote systems.

Re: JupyterLab: the next generation of the Jupyter Notebook

#14

Post by denfromufa »

mungoid wrote: post #11
m_ke wrote: post #8

Earlier quoted context omitted.

You should check this https://github.com/nteract/hydrogen/blob/master/README.md out.

Holy cow I never knew that existed! My life could have been so much different the past few months had I known.. I bet I even skimmed past it on HN without even looking.. Shame on me

In PyCharm it is possible now to work directly with jupyter notebooks. Even PTVS gained cell support recently.

Re: JupyterLab: the next generation of the Jupyter Notebook

#15

Post by denfromufa »

bicubic wrote: 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…

Notebook is still primary interface for final version of your analysis. But during iteration and experimentation of analysis, the other parts of jupyterlab are really helpful! Before all of these was not so nicely integrated.

Re: JupyterLab: the next generation of the Jupyter Notebook

#16

Post by denfromufa »

a_bonobo wrote: post #9

How does this differ from Rodeo [1]? [1] http://blog.yhat.com/posts/introducing-rodeo.html

Rodeo is python-only last time I checked. Also it is missing notebooks, widgets, extensions, rich outputs, server architecture, multi-user support. Rodeo is closer to spyder than jupyter.

Re: JupyterLab: the next generation of the Jupyter Notebook

#17

Post by p4wnc6 »

bicubic wrote: 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…

I agree, but would phrase it more like this: Jupyter has succeeded because each of the different major modes of interaction have been decoupled. If you just want to use it in a shell, you don't need to involve the browser at all. If you want a narrative format for sharing, presenting, or converting to slides, you can easily launch that environment.

This feels like a big step backwards for me too. It's effectively like replicating the MATLAB / Octave / PyDev (Eclipse) sort of IDE-with-extras-plus-console that is so, so cripplingly bad, but acting like it's great and new just because it's all in the browser.

If you're a fan of productivity, you shouldn't want to do that kind of stuff in a browser. Heck, I even disable all of the dropdown menus in Emacs because even that is too much of a productivity hindrance / inefficient use of monitor space when I am writing, reading, and thinking about code.

This is one of those things where I feel that it doesn't actually solve practical use cases, doesn't make people more productive, but because there is a big hype engine behind it, it gets adopted and talked about anyway, and eventually becomes the sort of thing that an Office Space kind of manager starts to force you to use ... which really scares me. Stay off my lawn.

Re: JupyterLab: the next generation of the Jupyter Notebook

#18

Post by denfromufa »

mungoid wrote: post #7
cauthon wrote: post #2

So RStudio in a browser? Jokes aside, this looks great. The biggest frustration I've had with the notebooks is the organization of code. Nice to see that become a bit more compartmentalized from the execution window.

Totally agree. My larger notebooks get pretty ugly and I have to spend a fair bit of time cleaning them up. But that's probably because I am not the most organized person ever.

That is why it is better to keep a jupyter terminal or qtconsole around for quick and messy experimentation connected to the same kernel before pushing it to notebook

Re: JupyterLab: the next generation of the Jupyter Notebook

#19

Post by zem »

m_ke wrote: post #8
sorenjan wrote: post #6

I love Jupyter notebooks, I just wish I could use them in a dedicated program instead of having to run a server and using a browser based client. It feels hacky and I just prefer native apps for coding and the browser for reading documentation and similar. Even an Electron based program that could be associated with notebook files and hide the server-client model would make it nicer to use. At the moment I like to op…

You should check this https://github.com/nteract/hydrogen/blob/master/README.md out.

whoa, that looks brilliant
Post reply on HN