924 karma · joined October 20, 2013
However it was definitively fixed in a kernel update about 5-10 years ago. I haven’t seen it since.
Given it has a half-life of around 40 minutes and isn’t a decay product (even via irradiation) of anything that’s found in uranium ore, I think that’s quite unlikely.
It may occur somewhere else in nature, very briefly/rarely, however.
We were at least honest in the interview process regarding hours, there are companies where you would only find that out after starting. There were people who were willing to go through that pain and I think they would agree they were well rewarded but I understand some people want different things from their careers.
That’s basically equivalent to betting on options (but wrapped up in a way that looks simple). Always remember XIV.
I believe any death is automatically referred for review, even if there is no evidence of wrong doing, as it’s so unusual.
Code doesn’t have to be branch free, just branch in a predictable way.
Statically branch free code is great when you have things that are genuinely unpredictable, think branches driven by data. You might reach for min/max as an example of that, but in most cases these tend to be highly predictable. Control flow in a decompressor is probably a better example (eg. literal vs copy).
If you don’t try and push the boundaries it’s fine (and if you make everything unsafe you’d also be fine), but otherwise life quickly becomes painful.
If you are going to go to that level of effort then you’ll find it much easier in c++ and the downsides of c++ become insignificant.
On the other hand if you’re writing a web backend c++ would be a terrible terrible choice.
I would not say the word is being misused.
An AIM-9X can do this, but the kill probability drops rapidly as you move off boresight.
Certainly Bloomberg is a much better value proposition (functionality divided by cost), but of course there is a market for cheaper and less capable options.