

Python’s pip and RubyGems have been around for many years prior, fyi.
And PHP’s PEAR, and Perl’s CPAN


Python’s pip and RubyGems have been around for many years prior, fyi.
And PHP’s PEAR, and Perl’s CPAN
But the OP complains specifically about typeof NaN, and not about Math.sqrt(-1) // NaN
I know this doesn’t count as “normal use”, but in Python you get it e.g. via math.inf * 0.
$ python
Python 3.14.4 (main, Aug 20 2026, 10:41:58) [GCC 15.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> type(float('nan'))
<class 'float'>


I only objected to the use of “only” in the comment above. I’d like to object to “never” as well.


I am a big fan of ISO8601, and I only objected to your use of “only” in the comment above.


…or your file manager is smart enough to do numeric sorting


People slowly learned to use their keyboards for proper typography?


It’s about Typescript compiler
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 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.
It was curious to me how he takes the PHP vulnerability as an example. You can have your stack of one component: PHP, and you’ll be vulnerable.