Jonatan Kłosko

Technically we could deprecate `Kino.Control.button/1`, because subscribing works for inputs also. Or we could use a different naming like `Kino.Input.counter/1`, except in this case we don't really need to show...

@josevalim not even because of form, you can already do that, but rather because we support subscribing to inputs, so it would be like this: ```elixir button = Kino.Control.button("Button") Kino.listen(button,...

The button input is essentially a stateful button control.

> Let's say we've 2-3 heavy DB queries and I want to create a report that's available as app. Ideally, automatically refetch the data at some interval or when user...

@josevalim ah you mean a function message, I don't think we do that anywhere, but sounds good. Don't we still want to show warnings and errors when running tests though?

@josevalim FTR we use `lang-python`, it already provides some completion in the cells, but it's only very generic stuff and builtins, not aware of the environment. Once we get to...

For more context, the reason for this behaviour is that we don't explicitly track which competitors quit. Instead, when looking for replacement, we look at the previous round and effectively...

> We cannot guarantee that code that we expand in one node for Elixir v1.18 will work on v1.17 or vice-versa. There were actually issues in the past, hence the...

Pretty sure the issue is specific to the dynamic slice inside while, I already run into this in several places, and removing the dynamic slice from the code makes it...

Yes, this appears to be solved in 0.1.1. The example from @abrasumente233 also works. Thanks :)