Oh no. What the article describes ends up with a real mess. If you set out to support a certain language you'll have a global view of how things should fit together, and what the implementation should do.
It's not enough to have a nicish abstraction, how did it work in practice and eek out performance? I've heard Bryan Cantrell say there wasn't much there and would be curious to really know what the truth is and more explanation on both sides.
The completion is a click away. If you can't deliver enough value for people to change the defaults or go to your site are you really doing a better job?
This is Soviet propaganda. The real number from Nagasaki and Hiroshima was about half of the casualties were instant. Furthermore fallout is much more understood: after a few short days of hiding inside, the radiation levels will have fallen to where normal life can largely resume without fear, reducing the number of slow casualties.
Do you have any sources to back these claims? Also, what specifically do you mean by "half the casualties were instant"--is it that "of those who died, half of them died instantly" or "of those killed and injured, half of them received their injuries instantly". Or is it some other thing?
I think you're falling into exactly the sort of trap I was talking about, that the enormity of the devastation is so unimaginably great that it's difficult to imagine what it would actually be like, and to (somewhat lazily) conclude "well, it'd probably be instantaneous". But, for example, this analysis doesn't support that idea at all: https://thebulletin.org/2020/08/counting-the-dead-at-hiroshi...
Your source says "most died on the day of the attacks, and all within a few months". Your source also says that cancer rates are not as high as commonly believed.
In Scandinavia we're still sending samples of hunted wild boars to check for cesium. Large parts of Belarus are quite contaminated and the local tyrant is the reason we know very little about how it affects the population in those regions.
I have a little experience on this aspect. There are tons of local governments who weigh in on the location of these lines and that can be a contentious process to get buy-in from them.
It helps there are automated tools for converting old style K&R function declarations to the new ANSI/ISO style, like protoize.
But K&R C is now so dated, protoize was removed from GCC 4.5 and onwards. When (in a bout of idiosyncrasy) I wanted to convert some ancient K&R C to new style a couple of years back, I ended up putting GCC 4.4 in a Docker container to make it easier: https://github.com/skissane/protoize
I'm not certain about OP's objection but for me it's less the function name and more the terrible history of how PHP tried to automatically fix SQL injection and instead made everything a thousand times worse. If you're not using bound parameters for user data you're taking a huge risk and making your life multitudes more difficult. PHP's PDO is by far the better option at this point but it suffers from poor enough usability that I've built my own wrapper for it at two different companies.
Why should I blame MySQL? It's the PHP developers that decided to introduce it and not change the name, plus have several functions that don't do the right thing as well.
reply