TCL & CMake are fully stringly typed. Both pretty terrible languages (though TCL can at least claim to be a clever hack that was taken far too seriously).
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. I think the smallest number of number types you can reasonably have is two - f64 and arbitrary precision integers types. One of the few good decisions Python made.
Terrible title. The article is about the risks of everyone using GitHub. That doesn't mean GitHub is destroying the open source ecosystem. In fact it's the complete opposite - GitHub massively helps the open source ecosystem. That's why everyone uses it in the first place!
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!"
because someone believed an ANSWER on a different question answered my question
Yeah that is actually their official position. Your question is duplicate if an answer elsewhere might answer it, which is clearly absurd. Essentially they think "what's 1+3?" is a duplicate of "what's 2+2?".
I think fundamentally they gamified moderation too well, and for many people they turned the site into a mod-maxing game, which obviously makes it an abysmal place to be for normal users.
It's not as simple as that, depending on the architecture. Typically they would fetch 64-byte cache lines so your 128 bytes aren't going to be magically more cached than 128 bytes on the heap.
Avoiding allocations may help but also maybe not. This is definitely in "I don't believe it until I see benchmarks" realm. I would be really really surprised if the allocation cost was remotely bad enough to justify the "sorry your file is too long" errors.
TCL & CMake are fully stringly typed. Both pretty terrible languages (though TCL can at least claim to be a clever hack that was taken far too seriously).