Super nice! It's only missing auto-complete and it'll be light-years ahead of other tools on terms of usability
There’s already a PR for it with a video of autocomplete in action :) https://github.com/elixir-nx/livebook/pull/208
Livebook: A collaborative and interactive code notebook for Elixir
41–50 of 87 posts
Re: Livebook: A collaborative and interactive code notebook for Elixir
#42Earlier quoted context omitted.
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.
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 p…
Re: Livebook: A collaborative and interactive code notebook for Elixir
#43These guys are amazingly productive, while also running a commercial company
This is software that directly helps their business, so it's not really productivity outside of their business endeavors.
This is tremendous work, they're running their business and come up with generic/generalisable solutions instead of narrowing the outcome to their own benefits only.
Re: Livebook: A collaborative and interactive code notebook for Elixir
#44Earlier quoted context omitted.
Be careful, websockets are tricky to secure and get right. It's easy to do something like forget to check the origin and now you've opened up a whole class of cross-site websocket scripting attacks. I love the idea of easy access and nice UI to prod machines, but put it behind a secure proxy or VPN layer and not facing the public internet.
'Connect to an existing node' is likely implemented using ERTS ( http://erlang.org/doc/reference_manual/distributed.html ). So you're basically connecting to the runtime of the target node. The security model for ERTS isn't great, though, so your point stands. All you need is a matching secure cookie and you can connect and run any commands you want.
The problem is that it's one password for the node network, and you either have it, or you don't. So there's no real administrative control over access; it's shared password.
Re: Livebook: A collaborative and interactive code notebook for Elixir
#45So this is like Jupyter notebooks for Elixir?
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…
Re: Livebook: A collaborative and interactive code notebook for Elixir
#46Re: Livebook: A collaborative and interactive code notebook for Elixir
#47Is it just me or is Elixir being talked/written about more in the past couple of months?
A bunch of startups including my own bet big on elixir 2 years ago and are starting to launch and gain prominence. the first wave of early adopters are coming out with battle stories to share and the conclusion is that elixir is the real deal.
This makes me even more excited to start an upcoming new position writing Elixir full-time!
Re: Livebook: A collaborative and interactive code notebook for Elixir
#48Is it just me or is Elixir being talked/written about more in the past couple of months?
It is growing and having good adoption. Not a huge language but it also has a fair share of novel features (being built on Erlang) that aren't commonly seen with other langs. So I think it might have a disproportionate visibility compared to size. Lots of work happening in the community, lots of ambitious ideas and releases.
Re: Livebook: A collaborative and interactive code notebook for Elixir
#49"connect to an existing node" is going to be amazing. I imagine two interesting uses for this. 1. producing reports. Connect a livebook session to your system in prod, run a livebook (which pulls data from DB eg), then get back a report. User engagement, cloud resources consumed, p90s, or an incident report... 2. manual database intervention. Suppose you need to manually make a batch of changes to the DB. It would be…
Re: Livebook: A collaborative and interactive code notebook for Elixir
#50Earlier quoted context omitted.
This is software that directly helps their business, so it's not really productivity outside of their business endeavors.
Try not to sound like you're diminishing the efforts and accomplishments of others. This is tremendous work, they're running their business and come up with generic/generalisable solutions instead of narrowing the outcome to their own benefits only.
Not really sure how it sounded like I was diminishing the accomplishments of others. How would you have phrased the point?