soweli Neko
@nekotachi.bsky.social
she/her(/they/it)
rust contributor
enjoyer of tcgs
native english speaker, conversational toki pona, very basic japanese
anarchist
#oponaemi
rust contributor
enjoyer of tcgs
native english speaker, conversational toki pona, very basic japanese
anarchist
#oponaemi
hell, make it a sponsored video for one of those translation services!
i'm sure there's an angle here somewhere.
i'm sure there's an angle here somewhere.
November 11, 2025 at 5:52 AM
hell, make it a sponsored video for one of those translation services!
i'm sure there's an angle here somewhere.
i'm sure there's an angle here somewhere.
Like, surely there's some random variety channel with 1.5M subs that would just eat this up, right?
make it one of those free vs cheap vs expensive type videos idk
there's no reason for this video to not exist in the current world
make it one of those free vs cheap vs expensive type videos idk
there's no reason for this video to not exist in the current world
November 11, 2025 at 5:50 AM
Like, surely there's some random variety channel with 1.5M subs that would just eat this up, right?
make it one of those free vs cheap vs expensive type videos idk
there's no reason for this video to not exist in the current world
make it one of those free vs cheap vs expensive type videos idk
there's no reason for this video to not exist in the current world
you can hotreload a driver for a controller and not even have to restart the game that is using that controller most of the time.
November 10, 2025 at 9:45 PM
you can hotreload a driver for a controller and not even have to restart the game that is using that controller most of the time.
that's the idea, yeah!
November 8, 2025 at 7:14 PM
that's the idea, yeah!
yeah, so my approach would be to have everything be inferred internally, but then at your public API boundary, you make all your entrypoints have explicitly annotated capabilities.
that way if you want to add a capability, you only need to change the inner and out function, not the stuff between
that way if you want to add a capability, you only need to change the inner and out function, not the stuff between
November 8, 2025 at 7:13 PM
yeah, so my approach would be to have everything be inferred internally, but then at your public API boundary, you make all your entrypoints have explicitly annotated capabilities.
that way if you want to add a capability, you only need to change the inner and out function, not the stuff between
that way if you want to add a capability, you only need to change the inner and out function, not the stuff between
The reason I do this a lot is because this repo has thousands of issues and only a few dozen of them are labeled "easy". I think it's good to have a well documented and diverse backlog of low-priority "easy" issues.
November 8, 2025 at 4:53 PM
The reason I do this a lot is because this repo has thousands of issues and only a few dozen of them are labeled "easy". I think it's good to have a well documented and diverse backlog of low-priority "easy" issues.
