Dead code elimination but with a different name for some reason

I used them heavily, but I still run into issues of guessing what type library functions return or expect me to pass in. Sometimes there was no answer because the authors I guess wanted to be cool and accept any type that kinda fits, or they return either this or that type based on the arguments and now I have to assert which one it is to the type linter. And then I’d still get runtime errors about failed property accesses deep in library code and have to figure out wtf they wanted me to do.

Eh, Python has a very small slice where I’d consider it the right tool for the job for me. It’s for when I want a less awful bash script, but going much bigger than that makes me miss type systems.

okay, let me elaborate: the hardware acceleration requires custom software to interact with it yes, BUT, they probably still use ffmpeg and just pass -vcodec custom_thing to it

ffmpeg codec

C’s compiler prevents common type bugs and handles things like register allocation for you? So does skill.

A null pointer exception is technically memory safe, you can get equivalent behavior with .unwrap() on an Option in Rust.

The Bill and Melinda Gates Foundation lobbied against waiving intellectual property laws that would’ve let countries produce the vaccines themselves. Instead, only the pharma companies that owned the IP could produce it, and those vaccines were immediately gobbled up by wealthy countries leaving millions in poorer countries without a vaccine. So no, he’s not one of the good ones, his philanthropy is still evil with a hint of good purely to launder his reputation.

Who says this is JS? Might be Rust.

Immediate mode rendering and components seem to be why people use them. And you know what? The web should natively support those but doesn’t (well it kinda bad components, but ehhh). Otherwise I agree, the frameworks are overcomplicated.

body {
    background-color: pink!important;
}

Number = IEEE-754 double precision float, which includes NaN, so it makes sense

Could definitely be worse for latency in particular cases, but if we imagine a write heavy workload it still might win. Writing a byte/word basically has to do the same thing: read, modify write of cache lines, it just doesn’t confuse the dependency tracking quite as much. So rather than stalling on a read, I think that would end up stalling on store buffers. Writing to bits usually means less memory, and thus less memory to read in that read-modify-write part, so it might still be faster.

A lot of times using less memory is actually better for performance because the main bottleneck is memory bandwidth or latency.

Also, optional value semantics. I love value semantics!

Minecraft mod users are the worst. They’ll post a screenshot of a version mismatch or dependency error that literally tells them how to resolve it and ask “hey, this mod isn’t working, how do I fix it?”

These things add up if you’re doing them all over a 1 million line codebase, by which point it’s incredibly painful to claw back performance if you need it.

Is that the JS bundle only? I think you’re forgetting the need to ship a rendering engine, a JavaScript engine, and the rest of the JS you inevitably bring in if you’re using something like React.

React

Probably because the only plausible takeaway from the image is “haha woman hypocrite/dumb”. If it’s not that, I have no idea what it is.