" @kirakira@furry.engineer i made a shitty port of rust’s serde library to ts/js because every guide i saw for serializing/saving player data in godot was horrifying to me
lb: i dont care about job titles or jobs. i dont want to work for a company i just wanna be useless and make art!!
you know, moving across the country wouldn’t be so difficult and expensive if the us hadn’t stolen so much fucking land. i think they should give all of it back
Δ-44203.1 'Carbon'
this is such a robocoded episode.
I don't want to be on the blockchain. I don't want to mint NFTs, I don't want to vibe code. I don't want to beg you to hit the 'subscribe' button and ring the bell. I don't want to game the algorithm for your likes or your views or your shares or to be on the first page of results or to get recommended. I don't want you to gift Nitro to my server. I don't want the thumbnails of my videos to have a red circle and question mark next to a faked expression of surprise, I don't want to pay for items that gives me an advantage over other players. I don't want you to take a moment to hear about today's sponsor. I don't want to pump a meme coin, I don't want to craft prompts, I don't want to influence. I don't want you to watch me react to watching a video.
I'm seriously sick of this shit. All of it.
when there is a fops napping in your lap youre not allowed to move until it leaves these are the rules
i can’t listen to podcasts or watch videos because most of the time i want to be listening to music. like, i have turned down sex on multiple occasions to go to a concert or because a new album released
sometimes i wish i were able to pull off the high femme cutesy girl aesthetic but then i remember i would miss being genderfucked
javascript optimizations are always super weird to me and i end up profiling bizarre things
today, i wanted to be able to provide default implementations to either plain javascript objects or ES6 class instances, so i had something like this
class DefaultImpl {
constructor(methods) {
if(!isPlainObject(methods)) {
return methods
}
this.methods = methods
}
aMethod() {
return this.methods.aMethod?.() ?? someDefaultImpl()
}
}
and my first thought was, “i wonder if i can overwrite aMethod when its called with either the default or given implementations to avoid the null coalescing check?
// ...
aMethod() {
if(this.methods.aMethod != null) {
this.aMethod = this.methods.aMethod
return this.methods.aMethod()
} else {
this.aMethod = someDefaultImpl
return someDefaultImpl()
}
}
}
the performance results for both approaches were identical on v8, spidermonkey, and JSC. i’m assuming this is because the shape of a prototype is highly optimized and the one that overwrites the function violates the browsers expectations and suffers a performance penalty while the other one doesn’t? and if that’s the case, maybe the null coalesce vs the prototype change ends up being a wash. or maybe branch prediction on the null coalesce makes the performance hit basically nonexistent? i’m not sure yet
finally, a clock that doesn’t have too many numbers that even I can understand