airbreather

joined 2 years ago
[–] [email protected] 8 points 2 days ago (1 children)

Updated title is now:

Japan's PM Ishiba denies talk he will quit following election drubbing

[–] [email protected] 180 points 1 week ago (7 children)
[–] [email protected] 7 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

127.69.420

127.69420

127.42069

[–] [email protected] 66 points 2 weeks ago (10 children)

no that's "Invisible". "Invincible" means it can't be divided

[–] [email protected] 21 points 2 weeks ago

The "only 800mb of free RAM" was a reference to how much Windows was consuming before the switch to Linux

[–] [email protected] 16 points 1 month ago (1 children)

Wait, this is a memes community... crap...

Uh... I mean...

Haha funny

[–] [email protected] 31 points 1 month ago (4 children)

False. The speed of causality is also c, so you would only have the extremely small interval of time represented by the difference between c and the speed of light in whatever not-total-vacuum exists between the Sun and Earth. Not 8 minutes.

[–] [email protected] 1 points 1 month ago

In a Neil Breen movie?

[–] [email protected] 9 points 1 month ago (3 children)

I'll figure it out

[–] [email protected] 5 points 2 months ago (1 children)

These are fun rabbit holes to go down. Everything here is true, of course: Big-O complexity isn't everything, context always matters, and measurements trump guesses.

But also, how many times have you encountered a performance problem with a slow O(n) solution that you solved by turning it into a fast O(n²) solution, compared to the other way around? The difference between 721ns and 72.1ns is almost always irrelevant (and is irrelevant if it's not on a hot path), and in all likelihood, the same can be said at n=500 (even 500x these numbers still doesn't even reach 0.5ms).

So unless context tells me that I have a good reason to think otherwise, I'm writing the one that uses a hash-based collection. As the codebase evolves in the future and the same bits of code are used in novel situations, I am much less likely to regret leaving microseconds on the table at small input sizes than to regret leaving milliseconds or seconds on the table at large input sizes.

As a trained practicioner of "the deeper magics" myself, I feel the need to point out that there's a reason why we call these types of things "the deeper magics", and that's because heuristics like "better Big-O means better performance" generally point you in the right direction when it matters, and the wrong direction when it doesn't matter.

[–] [email protected] 10 points 4 months ago* (last edited 4 months ago) (2 children)

FOSTA-SESTA is at the heart of it, as I understand. I don't want to elaborate much more because I don't know nearly enough about the situation, but adding this search term helped make it make a little bit of sense to me.

Edit: not that I'm lumping these different ideas together, but that the prudish folks could theoretically use this legal framework to throw allegations that Visa/MasterCard would rather not have to defend against.

[–] [email protected] 14 points 4 months ago (1 children)

FYI a more pertinent link for these situations: https://dontasktoask.com/

view more: next ›