still is

/i3gang

skill issue

fun fact, the RFC introducing NAT calls it a “short-term solution”

https://www.rfc-editor.org/rfc/rfc1631

wait, does windows jit compile C++ ??

but it removed half the point…?

i know this is a joke, but i find it quite interesting those two words have completely different etymologies.

Grave as in burial site comes from an old proto indo european word for “dig”, while grave as in serious comes from french.

I mean, sure, you won’t stay alive for very long with a stopped heart.

I meant like, when someones heart stops and gets restarted again with cpr or a defibrillator or something. People often call that being dead, and coming back.

people say quitting smoking is hard. I don’t understand, I do it multiple times a day.

I know this is a definition in many places. I find it stupid and useless.

The heart beating is not a good definition of being alive in my opinion. The heart stopping temporarily doesn’t mean you died, you were just in terribly grave danger.

If a person is defined by their heart, what does that make a heart transplant?

utterly useless definition.

oh god the reason is even stupider then I expected

Because large numbers use the e character in their string representation (e.g., 6.022e23 for 6.022 × 1023), using parseInt to truncate numbers will produce unexpected results when used on very large or very small numbers. parseInt should not be used as a substitute for Math.trunc().

uh, why not?

sender stack =/= receiver stack.

different languages I presume

Now do it in tcp!

whats wrong? they’re the same value no?

md5 for example is already vulnerable. People have figured out how to manipulate data into having a pre-specified hash. Meaning someone could engineer deliberate hash collisions and serve you any file they like.

SHA-256 doesn’t (i think) have this issue, so far hah.

you have to fucking hope no one figures out how to backwards engineer the hashing algorithm you choose

even a dash, ngin-x, would do it really