Notices by you╭👺+300╭🐈x5╭⁂+3╭(Ⓐ+a (unspeaker@mastodon.social), page 2

@kaia bc if they said they were cumming/coming everyone would get horny and ruin the stream :D there's no unisex unisyllable word for orgasm that can also be used metaphorically so "im nutting right now" it is

@mangeurdenuage classic

#TUI #DAW in #Rust for #Linux, day N.

Dual #sequencer piped by #JACK into 2 instances of #Helm (#VST and #LV2) in #Carla.

Not pictured: 177 (2918) xruns.

Enough for today.

@lain considering it was in california in 1967 i would absolutely not be surprised if it worked on them

@lain @anemone @arcana why 1992

@kaia

https://ludic.mataroa.blog/ might have part of the answer to why that's the case. definitely tracks w/ my experiences in most computer toucher jobs

also data science depends on mass surveillance which is evil, so the sector attracts grifters and incompetents. ppl who know their shit can get burnt out easily

guess as long as they pay you well and don't interfere with your education, a stint there may be worth it for money and cv. but steel yourself and don't take it too seriously 🤷

@xyhhx

@dansup @pixelfed is there an option to make the modlog public?

@kaia and portable!

@MrHedmad

you are focusing on entirely the wrong thing.

what you started with (and the strongest point of your argument) is that this is a double standard ("toxic" already being a watered down version of the point.)

then when you were confronted, you moved to defending the weakest of your points ("anecdote vs. anecdote"). sort of like reverse motte and bailey.

this. whole. dynamic. is the reason for what is described in OP. sapienti sat

@kaia

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?

@lain well now i have

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

@ironchamber

yeah... sucks innit... some days i think i've got legit reasons to be like that, some days i think it's just self-defeating behavior i should reject

like if this project is just something to facilitate my own music making, i'd just develop in private and get it done sooner :(

but i also want to use it to connect with people over a shared interest in programming and art, like having this conversation for example :)

hell of a tradeoff, i want my work to have results already :x

@ironchamber

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 🤣

@ironchamber

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

@ironchamber

and this is based on some old code that used to work quite nicely for that purpose ... but i can't reuse it because reasons :(

which is a damn shame because i liked it way better than #ratatui :(

@ironchamber

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

anyone got a clue what's going on here?

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`.

there's this answer https://users.rust-lang.org/t/box-with-a-trait-object-requires-static-lifetime/35261/2 but it's from 2019 - did the language change?

what am i overlooking?

#rust #rustlang #lifetime #bug #ratatui

@ironchamber

That's definitely the case!

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...