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

Run code inline in Atom using Jupyter kernels

github.com

Post reply on HN
Print view View original

31–40 of 56 posts

Re: Run code inline in Atom using Jupyter kernels

#31

Post by nickjj »

minimaxir wrote: post #23
nickjj wrote: post #13

This looks cool but how does this translate to being beneficial in real world web applications? Often times the result of running some bit of code is to see the end result in a browser because the code resulted in sending a bunch of HTML or JSON as a response. Also in the above case your code isn't self contained to a block of code. Chances are you have a web server, along with a database and cache server. Most of my…

Jupyter Notebooks are more for statistical, iterative coding, not running an application.

Thanks. I wasn't aware of what Jupyter was.

I only glanced the top of the README which compares the project to what Light Table was trying to solve and then showed an animated gif of inline code evaluation examples.

Re: Run code inline in Atom using Jupyter kernels

#32

Post by olsgaard »

Wonnk13 wrote: post #17

Advantages of this over running a repl in an Emacs buffer and evaluating code that way? I've never tried Atom.

Honestly, I would say the main advantage is you don't have to learn Emacs.

Emacs is a very polarising environment and there are many programmers for whom it is simply not the right code editor.

Re: Run code inline in Atom using Jupyter kernels

#33

Post by ZenoArrow »

pjmlp wrote: post #7

> Hydrogen was inspired by Bret Victor's ideas about the power of instantaneous feedback and the design of Light Table. Good work. Although Bret Victor deserves lots of appreciation for his work, most of his ideas are actually how Xerox PARC workstations and Lisp Machines used to enable developers to program more productively. So if anything the best part of his work is making young generations aware of what the indu…

If you try hard enough, you could tie any new development to the past.

Lisp may have been the first language with a REPL (as far as I'm aware it was either Lisp or Forth), but REPLs have evolved over the years, and plenty of modern programmers were familiar with REPLs before Bret Victor's views on instant feedback became popular.

Re: Run code inline in Atom using Jupyter kernels

#34

Post by robinson-wall »

ced wrote: post #20

I haven't tried either, but atom-notebook ( https://github.com/jupyter/atom-notebook ) looks more promising to me. I hope they can integrate it well. With hydrogen, are there cells? What happens if I want to rerun everything? Will I get no output except the output of the last line?

I think they both have a place - atom-notebook (like the web version) for more structured use with cells, and hydrogen for ad-hoc ("Will this work?") anonymous execution while you're editing.

> Will I get no output except the output of the last line?

If the return value is one line, it prints neatly after the executed block. If it's more than one it inserts a little pane with the results, with options to copy the data or open it in a new buffer.

Re: Run code inline in Atom using Jupyter kernels

#35

Post by mungoid »

Suuure, now this gets posted after I JUST found out about it yesterday in a comment about the JupyterLab link.. Go ahead, rub it in more.. Seriously though, I never thought to look for something like this so I'm happy more people are finding out about it too. Even if there may be better alternatives, more people now know to look.

Re: Run code inline in Atom using Jupyter kernels

#36

Post by ced »

robinson-wall wrote: post #34
ced wrote: post #20

I haven't tried either, but atom-notebook ( https://github.com/jupyter/atom-notebook ) looks more promising to me. I hope they can integrate it well. With hydrogen, are there cells? What happens if I want to rerun everything? Will I get no output except the output of the last line?

I think they both have a place - atom-notebook (like the web version) for more structured use with cells, and hydrogen for ad-hoc ("Will this work?") anonymous execution while you're editing. > Will I get no output except the output of the last line? If the return value is one line, it prints neatly after the executed block. If it's more than one it inserts a little pane with the results, with options to copy the dat…

I agree, it looks like Hydrogen is a nice replacement for the REPL, whereas notebooks are a completely different workflow.

Re: Run code inline in Atom using Jupyter kernels

#37

Post by ced »

throwanem wrote: post #26
Wonnk13 wrote: post #17

Advantages of this over running a repl in an Emacs buffer and evaluating code that way? I've never tried Atom.

Same question, but s/running repl in an Emacs buffer/authoring in org-babel/ - I have a hard time seeing Jupyter and friends as anything other than a subset of what people have been using org-babel to do for years, and I'm not really sure whether that's an accurate perception or not.

Thank you for the babel reference, it looks interesting. From what I can tell, it's pretty similar. In a notebook I'm directly editing the code and seeing the results immediately, instead of switching back and forth between emacs and a browser window. That looks like a pretty big win for interactive development. Is there any babel feature that you think is missing in Jupyter?

Re: Run code inline in Atom using Jupyter kernels

#38

Post by peatmoss »

throwanem wrote: post #26
Wonnk13 wrote: post #17

Advantages of this over running a repl in an Emacs buffer and evaluating code that way? I've never tried Atom.

Same question, but s/running repl in an Emacs buffer/authoring in org-babel/ - I have a hard time seeing Jupyter and friends as anything other than a subset of what people have been using org-babel to do for years, and I'm not really sure whether that's an accurate perception or not.

As an org-babeler myself, and someone who has also used RMarkdown and Jupyter notebooks, I feel like these newcomers are quite underpowered compared to Org. Not to mention that mixing languages in a single doc is not possible / cumbersome with the others.

I do recognize, however, that being tied to emacs (the only complete implementation of org-mode / org-Babel today) is a liability. I wonder if some smart person will figure out a portable implementation in something else. Of course, it won't match the flexibility or extensibility of emacs, but perhaps it can still surpass Jupyter / RMarkdown.

I mention RMarkdown together with Jupyter simply because org-mode / org-Babel nearly addresses both the dynamic notebook use case as well as the document publishing use case (including nice academic feature like cross-references, which aren't supported in Markdown).

Re: Run code inline in Atom using Jupyter kernels

#39

Post by brians »

olsgaard wrote: post #28

What Jupyter Notebook is missing is a good text/code editor and what good text/code editors are missing is Jupyter Notebook like write and execute. This is the first example I've seen of the power that using Electron in Atom can give, and it makes me super exited!

What's missing from Edwin or Emacs with SLIME? Support for Python, obviously, but—that's solvable. Is there a more fluid execution environment in Jupyter?

Re: Run code inline in Atom using Jupyter kernels

#40

Post by pjmlp »

ZenoArrow wrote: post #33
pjmlp wrote: post #7

> Hydrogen was inspired by Bret Victor's ideas about the power of instantaneous feedback and the design of Light Table. Good work. Although Bret Victor deserves lots of appreciation for his work, most of his ideas are actually how Xerox PARC workstations and Lisp Machines used to enable developers to program more productively. So if anything the best part of his work is making young generations aware of what the indu…

If you try hard enough, you could tie any new development to the past. Lisp may have been the first language with a REPL (as far as I'm aware it was either Lisp or Forth), but REPLs have evolved over the years, and plenty of modern programmers were familiar with REPLs before Bret Victor's views on instant feedback became popular.

The way one interacts with the Xerox PARC and Lisp Machines environments is much richer experience than a plain REPL.

It was a graphical REPL that could embedd live objects, which were still active to further interactive changes.

Also the ability to have the whole OS exposed via the REPLs is hardly available in modern systems.

Not alk REPLs are made alike.

Post reply on HN