I wouldn’t say it is quite simple to do such a quality replacement in Photoshop. I’d argue that people with necessary skill level are rather rare.

The face is wrong

the ecosystem seems to have died about 2 years

Yeah, as I said elsewhere, less alive than before

it requires signing up to join the system

I think the point of the standard was that you don’t have to sign up with someone specific.

But in more general terms, of course one has to sign up with some bank or website or wallet that will receive the money or send the money.

AFAIK it was already working, though cumbersome to set up. Then a core enable stopped supporting it, and now it is less alive than before. However I’m not deep into the topic and the last info I got from this article.

There are efforts on a standard called Web Monetization

Framework allows replacing and upgrading screens as the core feature. But for Chad ThinkPad this is a great achievement: “Even the screen is upgradeable with some tricks”.

JS just implicitly does what you, typed language developer, would have to do explicitly

Well, you tried to appeal to a common logic, and I appealed to even more common logic. If you arrange 3 apples on a table in an array, and ask anyone to take the 0th apple, they will be confused.

0-based is just a convention, not a law of the universe. Only using integer-type numbers to address array elements is too merely a convention of some programming languages. And note that no one suggests using non-integer numbers here, only numbers of non-integer type.

Obviously, opinions vary here as well

Types are good

Opinions vary on this topic, apparently. There’s a proliferation of untyped languages.

Try interacting with anything that uses u64 and you’ll be a lot less happy!

I’m sorry you had to experience this, but in all my years of development I hadn’t.

…not actually quite as bad… While it’s UB for C, and it can return garbage. … the value it returns is 0x8000

0x8000 is garbage. Insane.

What does it mean to access the 0th element of an array?

Well, I think I’m happy to never have to choose a number type in JS. I also think that insanity is how C and Intel handle NaN conversions.

So by insanity you mean having just one number type?

I don’t think I’ll dive deeper than quoting Wikipedia:

Most fixed-size integer formats cannot explicitly indicate invalid data. In such a case, when converting NaN to an integer type, the IEEE 754 standard requires that the invalid-operation exception be signaled.

For example in Java, such operations throw instances of java.lang.ArithmeticException.

In C, they lead to undefined behavior, but if annex F is supported, the operation yields an “invalid” floating-point exception (as required by the IEEE standard) and an unspecified value.

In the R language, the minimal signed value (i.e. 0x80000000) of integers is reserved for NA (Not available).[citation needed] Conversions from NaN (or double NA) to integers then yield a NA integer.

Perl’s Math::BigInt package uses “NaN” for the result of strings that do not represent valid integers.

Could you recommend a language with a sane handling of 64b-NaN-to-32b-int conversion?

I wonder how it is with nan etc in other languages

Stylish addon with a simple CSS :is(html, body) { background-color: #c3f1c5; } or Tranquility Reader

Not only in IDE, but on webpages as well

Tree-shaking works on per function basis