Project Jupyter Celebrates 20 Years, Fernando Pérez Reflects on How It Started
data.berkeley.edu
data.berkeley.edu
[1] https://datacrayon.com/posts/programming/rust-notebooks/setu...
[2] https://plotapi.com/gallery/posts/showcase/pokemon-types-wit...
I assume the grand parent is, at least partially, referring to this essay [1]. Here, the browser and HTML/CSS/JS is complimented for its dynamic nature and low barrier to entry, similarly to Emacs. In that sense, VS Code, like Jupyter, is a perfect example of the webbrowser gaining functionality of Emacs.
[1] https://steve-yegge.blogspot.com/2008/04/xemacs-is-dead-long... (the section: "The bad news: the competition isn't the IDEs")
I remember seeing new releases of iPython that enhanced the weird web interface feature and being utterly baffled as to why anyone would want that.
I finally got on board with Jupyter notebooks a few years ago and I've used them multiple times a week ever since.
I remember some of the postdocs were very nice and approachable. Others were very pretentious and cold.
One thing the other undergrads and myself would always talk about was how nice Fernando was. He knew everyone’s name, would take the time to give advice, casually chat, etc. - overall a great person.
Off topic: A big takeaway from working there was that those who accomplished the most were often the nicest. We’d have Nobel laureates come to and from the lab fairly often. They always seemed very grounded and passionate. The rudest people were overwhelmingly the ‘important’ bureaucrats and admin, with the occasional postdoc trying to make a name for themself.
tl;dr Fernando Pérez is an awesome person all around.
Gilad Bracha has also been going in this direction with his recent work on Newspeak and literate programming.
Is this how Smalltalk is finally going to gain adoption?
The current space to watch for literate programming seems to be Racket.
I just used iPython as a REPL because it was so much nicer than regular ole python (the unwrapped variant). Ipdb was nice too.
First, you have to install it, which if you don't use anaconda is going to be full of the usual gotchas.
Then you need to launch it, which because "-m" is broken on jupyter for windows, means people will have an extra hard time.
And then, once everything works, new commers still have to understand they need to create a notebook before entering any python code, find it back in their weird FS browser implementation and get how to execute and create cells.
Not a problems for any dev, but in class, it can quickly become a burden. Thanks to pyiodine, you can now use jupyter directly in the browser with no install at all:
Even using sqlite works :)
This is going to open so many doors for education.
I still think there is a room for a python scratchpad tool that would:
- be provided with a standard installer (exe, deb, .app) as well as with pip
- start with a fully operational shell (no need to create a file) but you can save it later
- show big buttons for common notebook operations near each cell such as "run", "add", "run and add", "delete", "duplicate" and "move"
- gui to deal install packages (and deal with venv when you decide to)
- use the currently activated virtualenv automatically
I haven't found a case where I have to commit to one or the other. My notebooks that work in one environment, tend to work in the other.
Strange title on the article itself. There is nothing on this topic in the article or the interview.
I guess that is why it's popular.
But honestly it's only a tiny small part of what it's for.
jupyter is mostly about explorating ideas, code and data. It gives you a comfortable env to quickly try something out. Sharing it with other is just the cherry on the cake, not the main goal. I mostly never share my notebooks, but I will fire one as soon as I want to try a new library, or need to extract data from a file.