ahh I see. it's the bytecode to native code step the browser does. I see. man that's annoying if that's the case

wasm is already compiled. the browser just runs it. I'd be curious if it is any faster if you do a release build instead of a dev build, assuming you're compiling from rust. not a good development flow but just to see if that speeds it up at all.

naw man. see? we need to move fast and break things. it's gonna be sick man. you'll see. just don't think about it.

oh shit. I can't un-see this now

vim.

I'm sorry. someone had to say it.

naw man. those nails would be painted.

wasm has to be fully downloaded and parsed before being run. devtools being open often means the cache is off. this means the wasm file is redownloaded and parsed each time. JS doesn't have this issue. browsers, I believe, can start running the code while parsing it.

that's retarded

gotta bitch about something

for the Linux users out there, what window manager and desktop environment do you use and why?

nostr:npub1j0sh8peshr8rthgn0hlh2mxqwaazne3kc3rqsm0y7ysssg77wd8smfga0n and I would start a mosh pit

i want to know the story behind this.

location event for location based apps

probably should just not workout. i'm sure that's the answer lol

starting the day off with a workout makes me wanna go back to sleep

man. this online safety bill is some shit, huh.

fix the macaroons. fix the world.

see what

damn. that sucks man. Bob has had lots of issues with his system76 too. I'm putting it on a starlabs machine. we'll see how nixos works on it. it's not an officially tested os. you'll have to let me know how the framework laptop is. I love the concept. would like to try one out.

I'm doing it. starting the transition to nixos for my daily driver tonight. God be with me.