Ah, I’ve misunderstood you - usually analysis tools provide best lines in standard notation, but single visualisation not bunch of boards. But at some point one can „see” boards by looking at lines 🤷🏻‍♂️

Yup, standard analysis tool

I’ve lived in communist Poland as a kid - whenever american tv host mentions communism, I can assure you they don’t know wtf they talk about

Add telemetry, connect to @honeycomb.io , solve the problem

This whole thing is dark as fuck

But only for a single window! 😂😂😂

Fast fash

So maybe you know how hard is to maintain for example rest api longterm, especially when you have already existing integrations. Events are your internal api - if your system is done and won’t be evolving then that’s fine, otherwise welcome to the world of event versioning and other magic.

Cqrs pretty good as a principle, commanded pita maintaining long term. I’d be very cautious before commitment

Reminds me of Maman: en.m.wikipedia.org/wiki/Maman_(...

While SaladUI seems promising I found it harder than I thought to incorporate. Naming is kind of weird and I was fighting it instead of just using. But that just me - wouldn’t recommend. Ash is awesome in some regards but for data eng work I prefer pure ecto - it’s just easier to write queries

Finally

There is none, because in erlang you think in processes and messages and one can easily ‚spawn’ a process (async) and then ‚receive’ a message (await). You could do it the same in elixir, but these building blocks are kid of hidden (I suppose Task is easier to grasp when you come from ruby)

I did rust + tauri which might be better option here. Worked like a charm