Livebook: Elixir's Swiss Army Knife
thestackcanary.com
thestackcanary.com
Livebook is incredibly powerful and versatile. When the general population finally wakes up to how insanely powerful Elixir is for such little effort, cost, and time to build (compared to other options) they will find an incredibly mature ecosystem of tools and resources ready for consumption.
Agree, and I'm eagerly awaiting this day!
Don't feel obligated to answer, but how has LiveView changed DockYard's approach to PWAs? Are you still pro-PWA? Do you still see (much) room for PWAs in a LiveView world?
Playbooks at work, exploration in personal projects, 80% of my terminal use is now driven by an editor and sending snippets to the terminal.
(I know this is more common for emacs and lisp users, but never really managed to get into that workflow myself, until livebook)
My only gripe is that livebook itself doesn’t love reloading if I edit the source files directly, and I’d like to get that working.
iex --sname some-name --cookie some-cookie -S mix
And then in the livebook, go to the runtime settings, select "Attached Node" and enter the name and cookie.It seems kind of inconvenient to have to do this every time, and also I don't get any automatic hot reloading of modules in the livebook when I edit files directly, so I just end up copying files into the livebook to edit them. Maybe there is a nicer way?
Wish I could just `mix livebook.start` or something to open a livebook attached to the current mix project. Or have that be the behaviour when opening the notebook file by default.
Edit: I just saw this comment from the previous discussion: https://news.ycombinator.com/item?id=37035686
This might be what I want actually!
eg https://www.thestackcanary.com/serving-spam-detection-with-x...