2

ohno I'm rewriting that async proxy swarm thing again

third time's the charm, right?

brain's a bit better so maybe I'll get rid of the weird mystery async hanging error this time...

and this time I'll have one persistence object instead of 4 scripts that all juggle loading the same files without running into each other through sheer wit (which now I'm so unsure of 😭, so fragile!). thanks tui

and there's a logging library called tracing that would let me access logs of innermost libraries if I log using tracing instead of print lines, then I can subscribe to the logs and get them in the tui to debug with them and bam. let's see how it goes. might work well for debugging async code. it's built to handle async logging actually

I'm not sure why a lot of rust libraries are a mess but with power of gp5 writing me demos I'm ticking along even if I run into dead ends... like how I gotta do my own text wrapping in tuis and it won't work with ansi codes. eesh. but that was only a couple hours detour of confusion at least instead of me getting too frustrated with it. I came up with a solution that works good enough and wasn't too fancy, phew

Comments
  • 1
    How can it work without ansii codes? Problem is, that AI is terrible with rust but regarding a tui, i recently vibed an editor using no ncurses. Just printing ansii myself. It's quite a challenge but it feels very good to have it natively working. But I'm sure this is possible within rust as well. Try to vibe a lib doing only that first, try to make a vim/nano-ish editor to test. Editors gets hard when you want to align the cursor with the actual document and stuff. I'm not talking about that part.

    But bottle neck is just rust. But this, since it's just ansii printing, should be possible with help of llm. Maybe it's a good idea to use les libraries since Rust stuff is hard in development and the llm probably always produces old shit.
Add Comment