Re:Livebook: A collaborative and interactive code notebook f...
by seanhandley on Sunday April 18, 2021 @11:54AM
(#26853516)
So this is like Jupyter notebooks for Elixir?
[ Parent
| on HN ]
Re:Livebook: A collaborative and interactive code notebook f...
by lawik on Sunday April 18, 2021 @01:15PM
(#26854319)
With google docs style collaborative editing, can connect to an existing cluster to run code in it. You can run one instance of the Livebook application and have different livebook docs run for different Elixir projects you happen to be working on.
Not sure what parts are in Jupyter but I've heard collab editing isn't.
Pretty hype about trying this for some living docs and teaching. Will see if I can do anything neat with it. Already tried it some.
Re:Livebook: A collaborative and interactive code notebook f...
by aleDsz on Sunday April 18, 2021 @11:54PM
(#26858975)
I used to teach my viewers of the basics of Elixir.
It's in Brazilian Portuguese, but it's kinda interesting how easy is to use Livebook and show some code for people.
Re:Livebook: A collaborative and interactive code notebook f...
by bostonvaulter2 on Sunday April 18, 2021 @07:19PM
(#26857487)
Yeah I think this will be really neat when paired with an example project for libraries.
Re:Livebook: A collaborative and interactive code notebook f...
by matreyes on Sunday April 18, 2021 @01:49PM
(#26854673)
If you compare the work done in both projects (github insights), you will feel the power of the Beam, Elixir, Phoenix and LiveView.
Re:Livebook: A collaborative and interactive code notebook f...
by rajandatta on Sunday April 18, 2021 @12:02PM
(#26853585)
Yes - it would seem so. The support for custom run times is interesting and seems like an improvement. Not sure Jupyter notebooks do that - certainly not for all supported kernels.
Re:Livebook: A collaborative and interactive code notebook f...
by nerdponx on Sunday April 18, 2021 @12:17PM
(#26853739)
Jupyter is great but it's somewhat of a "lowest common denominator". So there is always the temptation to make a more task-specific version; see also the Pluto notebook project for Julia and R Markdown (although the latter evolved concurrently with IPython/Jupyter, not after it).
LSP is in a similar situation right now, where it's great for languages that lacked tooling to begin with (like Python), but it's not yet possible to migrate existing powerful language tooling (Lisp SLIME, OCaml Merlin) to use LSP.