Nat (she/they)

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

I thought the joke here was that your unbalanced parentheses would make me angry (they did))

We already have nanoservices, they’re called functions. If you want a function run on another box, that’s called RPC.

Sounds like a distributed monad

I love their strong stance!

My gender is

{ toString: ()=>{String.prototype.toString = ()=>">:3"; return ":3";} }

And then the compiler updates to get better at spotting optimization opportunities and it blows up again

How convoluted was it?

Listening to employees when making decisions, what a concept! It’s a shame many places don’t do that.

Do you get two empty spaces next to your tower? For maintenance if the lower elements.

It’s called a tower PC for a reason

True, but we’re not talking about clear and up front rules

I’m not the person you’re replying to, but I am stupid enough to occasionally get close to falling for a scam. Rather than test my luck, I’d rather they didn’t exist.

Pick something and change it when inspiration strikes. Sometimes you need a big picture view of something to get the right abstractions or even just name things.

Indentation implies there’s some control structure causing it. Too many control structures nested gets hard to mentally keep track of. 3 is arbitrary, but in general more indentation => harder to understand, which is bad.

All human strings are finite…

Green threads are functionally the same, especially in languages that can preempt.

IEEE-754