components_guide VS livebook

This is fantastic. The specs and the MDN documentation are pretty detailed, but I’ve found I need a fair bit of trial and error to understand some WAT language features.

The loop with a block directly inside is a good regular pattern! I’ll be using that all the time now.

I’ve been writing an Elixir DSL for WAT. Elixir has a powerful macro system, so I can closer to that pseudo C-syntax in this post, plus some other niceties. I plan to open source it as a library soon.

Here are examples I’ve written in it, like an HTML escaper, stateful HTML component, bump allocator, and a few state machines.

https://github.com/ComponentsGuide/components_guide/tree/mas...

Livebook started out as Elixir's version of Jupyter Notebooks. Jupyter is pretty great. But it turns out that code notebooks on Elixir are something special; they do something you usually can't pull off in Python. That's because Elixir has powerful built-in clustering, built on Erlang's BEAM/OTP runtime. Livebook notebooks can talk directly to running Elixir apps. And so we can do analysis and visualization directly off the models in our applications.