fzzt

This appears to be a poorly-sourced "research" page put together by a marketing agency. There's really nothing there about the methodology of this work, and there's plenty to suggests the authors have very little knowledge of firearms (a fired bullet in the first animation is shown with a casing, there's no discussion of bullet aerodynamics which are going to be very different for most sharp-tipped rifle bullets and for handgun rounds, etc) or physics (e.g., no accounting for energy when evaluating the velocity at which a bullet can penetrate skull).

The prospect of the images getting "structurally" garbled in unpredictable ways would probably limit real-world applications: https://miro.medium.com/max/4800/1*RCG7lcPNGAUnpkeSsYGGbg.pn...

There's something to be said about compression algorithms being predictable, deterministic, and only capable of introducing defects that stand out as compression artifacts.

Plus, decoding performance and power consumption matters, especially on mobile devices (which also happens be the setting where bandwidth gains are most meaningful).

Yeah, it's usually a combination of these two factors. You live beyond your means for a decade or five, and then something else goes wrong: natural disaster, war, crop failure, sanctions, whatever. Situations that could be survivable otherwise trigger a downward spiral because you were pushing your luck before.

The history of coinage spans thousands of years. Despite the popular tales, spot barter was almost certainly not the basis of any real economies.

There is definitely some bias in the availability of data, but it was comparatively harder to end up in a hyperinflationary spiral in the era of commodity or representative currencies, and these were commonplace until the twentieth century.

There were instances of money suddenly losing all value due to the failure of the issuing state (e.g., confederate dollar banknotes), but that's probably a different story.

Many countries that suffer hyperinflation keep the historical name of their currency, but establish some exchange rate between the "old" and "new" money. Zimbabwe went through four cycles - currency codes ZWD, ZWN, ZWR, and ZWL.

Per Wikipedia: "The final redenomination produced the "fourth dollar" (ZWL), which was worth 10^25 ZWD (first dollars)."

The ZWL itself was subsequently largely abandoned, too. I believe you'd have more luck transacting in foreign currencies.

"Allied" in the sense of having a USSR-installed puppet government propped up by the massive presence of Soviet troops. This was a part of the concessions made by the West to Stalin, not an expression of the will of Polish or German people.

Teflon is very non-reactive and any small pieces you ingest should pass through unchanged pretty quickly. You likely ingest a lot more plastic from other sources.

Recessed lighting fixtures are a common cause of problems with LEDs due to poor heat dissipation. But a lot of newer homes have recessed lighting, and in at least some parts of California, the fixtures are now required to be sealed (I guess for overall house energy efficiency).

Many LED lightbulbs make claims about their expected lifetime. Except these numbers are often a fantasy. The LED itself may last almost forever, but the capacitors commonly go bad in a year or so.

I suspect that would be the reality with a lot of the proposed mandatory labeling for electronics, too.

A lot of these questions touch on important topics, but I think there are too many of them and they are far too specific - to the point where you might be inadvertently signaling some kind of unreasonable inflexibility ("you better be using a particular bug tracking system or else I'm out!"). I'd suggest generalizing and combining many of these. Asking the interviewer to walk you through the development process can be more revealing and is less adversarial than a rapid-fire of 30 questions.

Also, the likelihood that a candidate will be informed of any non-public plans to sell the company are slim...

> Maybe we don't want them to be able to do any of that

"We" who? Application owners want that, browser vendors want that (their greatest fear is that mobile will eat the web, so they don't want to make the platform less flexible)... and users generally don't mind.

> impossible for servers to know my password, hence impossible passwords leaks

That would require deeper architectural changes to HTTP auth, but is probably a reasonable goal. That said, it's more readily approximated with unique passwords + having a good password manager. The main risk of password leaks is not that they make that particular breach worse (since the attackers can just grab your data), but that passwords are reused too often.

Federated login is another approximation, where the password is only known to your identity provider, not to every identity consumer. It's modestly successful for some lower-value services.

There's a lot more to that. A bank doesn't want the "back" button to work forever; they want to control the lifetime of your session, ideally on the server. Google wants to let you sign into multiple accounts on the same origin. Many others want to have seamless single sign-on across several of their web properties. Sometimes, you want the change of your password to invalidate other sessions (say, when recovering a compromised account); other times, you don't want to kick out your smart thermostat and have to set it up from scratch.

Admittedly, there are some simple use cases where HTTP auth is all you need, but it's just way too inflexible, unless you turn it into some mammoth spec that is never going to be as flexible and tempting as managing user identity yourself.

Especially since HTTP auth doesn't actually mean you can stop doing that anyway. You're still handling account creation, password checking, all the abuse / bot detection bits... all you're getting rid of is the sign-on and logout functionality, which is really not that complicated to begin with.