The one option that is mandated by an ISO standard.

Besides, if max and min are going to have a value without any parameter, it has to be exactly those Javascript uses. Unless you have a type that define other bounds for your numbers. And null always have a pointer type (that is object in Javascript), for the same reason that NaN always have a number type.

The only one that is bad on that list is D.

Apart from dynamically typed languages which need to store the type with the value

You know that depending on what your code does, the same C that people are talking upthread doesn’t even need to allocate memory to store a variable, right?

And compiler. And hardware architecture. And optimization flags.

As usual, it’s some developer that knows little enough to think the walls they see around enclose the entire world.

GNU tar is easy and straight-forward.

It’s also completely incompatible with any other Unix, but then, what difference does it make is nobody can use them?

but now the computer science bubble is popping

It’s more of an anti-bubble where companies are keeping salaries down in an unsustainable way. Software development still has at least a decade of good salaries to go.

It’s not the first time this happened.

Nah, they are fairly common rocks.

We can even use extremely common ones, but the just a little bit uncommon ones need an easier forming spell.

You don’t know if she had cast fire-invulnerability on herself earlier…

Longer than the life span of the most long-lived star. By orders of magnitude.

I’d go with a prefix, so it’s ls-friendly.

Really-long term storage :)

SQL won’t judge you.

It normally means either some point on the strict/lenient/unityped spectrum the author thinks is strict typed, or static typed.

And yeah, it’s a useless name, we could as well use it for languages that make the developer break keyboards.

There’s no way to access free mail accounts other than doing that.

There are many Android Apps that connect to yahoo through the web interface and retrieve your email so you can read it in a normal place.

No problem, just use another AI to write reports about the vulnerabilities on the code and send them to the development team.

The Brazilian plug has none of those problems…

Also, what European plug are you talking about? There are quite a few models there.

It’s meant to basically go “yeah, sure I’ll fuck with that” and keep trucking.

Yet, it lives in an insulated environment, with plenty of infrastructure to make sure errors do not propagate, with a standard error handling functionality on the spotlight with specialized syntax, and with plenty of situations where it just drops the ball and throws an error.

Nope, not falling for the gaslight. It’s a stupid feature that’s there because the language was created during a week and the author was trying to juggle the requirement of a rigid and typed semantics that looked like Java with his desire to make a flexible single-typed language that looks like Lisp.

And nobody fixed it, decades later, because everybody keeps repeating your line that the interpreter must always keep on.

Nah, it’s stupid either way.

“5e-7” is not an int to be parsed. Neither is “0.5”.

Yeah… It’s extra work not to do this. Why would you make an endpoint and not throw in every property of that entity? Why would you mess with your URIs instead of making a clear division with logical entities?

Yet, somehow, most people do exactly those things.

You shouldn’t align code anyway.

If it’s important to have stuff on the same column, make it an indentation level and add a line break where it starts.

To add. The specific edge case where you want to do the balaclava thing is when you are concatenating internally generated column and table names, operators, and entire conditions with extra parameters that you will add the correct way.