Experience has shown that having a map as your only data structure is definitely a mistake. It's much better to support real arrays too. I doubt it would have made the implementation significantly more complex either (maybe even simpler for luajit).

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

Anyway JavaScript does have BigInt so technically you are choosing.

that insanity is how C and Intel handle NaN conversions.

It's not actually quite as bad as the article says. While it's UB for C, and it can return garbage. The actual x86 conversion instruction will never return garbage. Unfortunately the value it returns is 0x8000... whereas JS apparently wants 0. And it sets a floating point exception flag, so you still need extra instructions to handle it. Probably not many though.

Also in practice on a modern JS engine it won't actually need to do this operation very often anyway.

Yeah unfortunately these numbers don't really allow any conclusions to be drawn at all.

Also they're not really related to supply chain security which is more about deliberate subterfuge. I think the interesting stat there would be how many authors are being trusted typically for each crate.

It's because as soon as one country forces it on their citizens the others can say "it can't be that crazy - Australia and the UK have already done it!"

Wow, that activated some seriously ancient neurons... I just looked up some of the models it supports and surprisingly they were made within the last decade. For some reason there's still a market for cheap dedicated MP3 players.

I guess they cost basically nothing to manufacture and some people might need them...

I'm not sure I agree. I think most people can understand recipes or instruction lists and totally could program, if they wanted to and had to. They just don't want to and usually don't have to. They find it boring, tedious and it's also increasingly inaccessible (e.g. JavaScript tooling is the classic example).

But I think mainly people just don't find it interesting. To understand this, think about law. You absolutely have the intellect to be a lawyer (you clever clog), so why aren't you? For me, it's mind-numbingly boring. If I was really into law and enjoyed decoding their unnecessarily obtuse language then I totally would be a lawyer. But I don't.

After Dorsey sold Twitter to Elon Musk, selling the platform out to the far right for a crisp billion-with-a-“B” dollar payout, the FOSS community shouldered the burden – both with our labor and our wallets – of a massive exodus onto our volunteer-operated servers, especially from victims fleeing the hate speech and harassment left in the wake of the sale.

That is a very weird way of putting it. Like Mastadon et al didn't want more users? That's not at all the response I remember.

Yeah Verilog. That's literally the language people use to design chips and FPGA bitstreams.

Someone has already done it: https://github.com/Redcrafter/verilog2factorio

Languages that make use of references rather than pointers don’t have this Dualism.

It's not about references vs pointers. You could easily have a language that allowed "null references" (edit: too much C++; of course many languages allow null references, e.g. Javascript) or one that properly separated null pointers out in the type system.

I agree with your point though, using a special Null value is usually worse than using Option or similar. And nullptr_t doesn't help with this at all.

I agree Bluetooth (at least Bluetooth Classic) is not very well designed, but not because of frequency hopping. That improves robustness and I don't see why it would cost any more power. The hopping pattern is deterministic. Receivers know in advance which frequency to hop to.

Well yeah I think the point is you're human and you might make a mistake.

Yeah LaTeX definitely has some of the jankiest log outputs of any program. I just looked it up actually and it's basically a warning that that but it the document might not look great (I guess something like in newspapers with justified columns where you sometimes see s t r e t c h e d w o r d s.) Definitely insane to print warnings like that by default. Maybe it made more sense in the 70s?