

It *is* convenient for developers, though, for pretty much the same reason: you don’t have to think as hard about locking and whatnot because the compiler is checking your work.
Previously @argv_minus_one@mstdn.party


It *is* convenient for developers, though, for pretty much the same reason: you don’t have to think as hard about locking and whatnot because the compiler is checking your work.
Hmm good point.
Personal preference. 😛 Figured since I’m in my 40s, I shouldn’t be quite so crass as I was when I was young.
I mean, those aren’t just good s**ts. Those are *advanced* good s**ts.
I suppose you’re going to also brag about your fast car, huge mansion, and handsome spouse? 😛
In normal Earth, you eat the body of Christ.
In post-apocalyptic Earth, the body of Christ eats you!
I don’t think it counts as “overalls” if it only covers half his torso.
It’s a bird! It’s a plane!
Should be in your Google account settings at “Security & sign-in” → “2-Step Verification” → button at the bottom labeled “Turn off 2-Step Verification”.
…I think. I might be wrong.
You realize you can turn off 2-step verification in a Google account?
There are some sites/apps where multi-factor authentication is mandatory, but Google isn’t one of them.
And yeah, I leave 2-step verification off for this reason. What if I lose my grip on my phone and it falls into a river? Losing my phone is bad enough; losing my Google account would make it even worse!
KIDDOS used LOGIC! It’s super effective!


I’m talking about the *code* wasting memory. In JavaScript each function is a heap object and its source code is another heap object. Even if a JIT compiler inlines them, the original non-inlined functions keep sitting there wasting perfectly good bytes.


That might have been a reasonable statement 3 years ago, but today there is a global crisis caused by extremely high RAM prices. Optimize your blasted code.


I am admittedly a bit…emotional about not wasting memory. Growing up on a 486 with 4MB of RAM does that to you, I guess.
The extra function will only be slower if the compiler/interpreter doesn’t inline it, which most compilers/interpreters including JavaScript will, so it’s mostly just a memory-usage issue. But I have used rather simple interpreters that *don’t* inline functions, and one of them even came with a warning that function calls are slow!


A function should be short enough that you can read and understand it.
Unless you’re using a language in which each function declaration has a performance or memory-usage penalty. Not an issue if your language compiles to machine code or WebAssembly, but interpreted languages like JavaScript do have such a penalty. In these cases, you may need to make your functions longer to avoid that penalty.


And also instantly changes your outfit. Convenient!
I mean, it’s not wrong.
@nebeker
Yes, exactly. I’m trying to write good code, so I appreciate tools that make it inconvenient to write bad code.