sadly it could be anything (last time this happened to me i narrowed it down to a kernel bug triggered by me plugging in the lan cable) i assume you've checked system log / dmesg?
thank #rust for type inference working as expected!
this week the #tui#daw saw yet another extensive refactor (finishing it right now instead of working on my emigration)
the ui code was once again becoming rich in accidental complexity, so i sighed a big sigh (remember breathing?) and started cribbing from that code i wrote 2 years ago (before i went through... "all that")
turned out different enough - private ai models may still be able to identify me as the same person but not public ones
on one hand who's gonna doxx me over reusing my old code, and what's the chance they're gonna do anything to me - on the other even if the chance is minuscule the consequences would be beyond what i can deal with currently - so let's rewrite everything from scratch but worse 🤣
yeah.. the only thing I like about ratatui really is the double buffering
a couple years back i wrote my own framework on top of crossterm, was quite happy with how it let me compose things
generic over backend too (business logic could theoretically be reused with a gui backend instead of tui)
but i put it on github. and then something something trauma ostracism paranoia so now i can't reuse stuff that i've published on github because it's too connected with my past identity
hmm, i'm not sure i'm parsing your suggestion. is "pop something out" something that i should try doing, or is it a possibility that i need to account for?
the goal is to compose `Render`able widgets inside the `render` method of other widgets
Collected::Box is for when they are ephemeral (owned by the render method) and Collected::Ref is for when they are stateful (owned by the parent struct), if that makes sense
i know what the error message means, but i don't understand what causes `'static` lifetime to be required, considering I've explicitly specified the `'a`.
Granted, I'm not the best at tidying in the physical realm. Didn't see the point of it at first - until I had the realization that it's kinda like managing the entropy of things by pointing your attention at them 🤪
Over here it's the opposite: if I've embedded a few sketchy assumptions and moot points just to reach a milestone (as was the case here), my focus just fails to latch in "forward", and I end up alt-tabbing editor<->doomscrolling all day 😪
People have been cross at me for what's probably one of my most disruptive #programming habits, but the truth is - when velocity grinds to a halt and you find yourself inexplicably #stuck, like you just don't know what to do, just take a deep breath and... #refactor the hell out of the whole damn thing, preferably in one sitting, like a complete and utter #madman.
Meanwhile, looks like this project has crossed the 5000 #LOC barrier like wheeee...
Pushing an unfinished #commit makes me anxious. So do big refactors which may not pay off.
Yet, having to spend a couple days sitting down in a moving box without #Internet, I had just enough sitting down time to go about halfway through this one.