anttihaapala

I had to check all of our Python deployments and installation BOMs and was quite relieved - turns out that none actually installed brotli libraries. HTTP libraries like httpx, requests and frameworks consider them optional and autodetect their presence.

Yes it has been. I have had a second level .name for 20 years.

Malaria was endemic in Finland until the beginning of the 20th century, the people used to lived inside smoke-heated chimneyless log cabins together with animals, mosquitoes... and Plasmodium vivax...

The problem is for most practical uses where you need fast calculations the 64 bit precision is enough. For example there is hardly any physical calculation that would need more precision. 64 bit float can be used to measure the Earth-Sun distance to 30 micrometre precision. 128 bits does not just add anything generally useful. For monetary calculations you should be using decimals instead of binary anyway.

How about everyone gets a digital certification from their own government that this is the person named this and that. No need to share cranial measurements and iris scans.

formatting should definitely be in pre-commit though, otherwise you'll destroy diffs.

This is not a complicated algorithm. A hash map (dictionary) or a hash set is how you would always do deduplication in Python, because it is easiest to write / least keystrokes anyway. That is not the case in C though, as it is much easier to use arrays and nested loops instead of hash maps.

Yes, and while waiting for the child services to intervene then those children would still be starving.

If you consider an underwater cable running from Finland to Germany or Sweden to Lithuania in the Baltic Sea, it is virtually impossible for a ship travelling from St. Petersburg to the Kattegat to avoid passing over it, so redundancy can do only that much there.

Yet Vietnamese can be written in Unicode without any combining characters whatsoever - in NFC normalization each character is one code point - just like the U+1EC7 LATIN SMALL LETTER E WITH CIRCUMFLEX AND DOT BELOW in your example.

Oftentimes many of the significant new PHP features are to fix the shortsighted implementation in the previous ones - for example this method chaining with `new` - there was precedent already, C++ got it right well before PHP even existed and with the very same arrow operator that PHP borrowed (and so did Java and JavaScript with .), so the question is why did PHP have to get it wrong at first and for so long.

Another pet peeve of me is that the global namespace is littered with these utility functions that should be easily composable or maybe be methods on the objects themselves - and looks like PHP 8.4 adds four more `array_*` functions. For comparison, Python's builtin namespace has a total of 71 functions and a couple of exception classes. PHP's builtin namespace has more functions for dealing with arrays and now 58 of those are prefixed with `array_`.