Not a loss but a cost/expense. A loss is, to put it simple, when money in - money out < 0. Without having looked it up, I would imagine that most of his wealth is tied to amazon stock.
I’d assume it’s a ”typo” as well. Most likely it’s not the same person hiring and writing the job ad. So a qualified guess would be that a character got lost during communication/translation.
You didn't understand this sentence: "Simply buying a new cable does nothing to fix that because the springs are in the phone." With Lightning, the springs are in the phone. With USB-C, the springs are in the cable. Springs are a moving part, and thus especially vulnerable to wear. Replacing a cable is cheaper than replacing a phone.
I did. The springs wearing out very much means bad contact at the contact points, we do agree there. However the receiver end with gold plated contacts points do also wear out. I’ve yet to see anything pointing towards springs wearing out before the gold plated areas (that is being worn by friction each insertion/removal) do.
I’ve got a Lightning cable with worn out gold plated contact points, the springs in the phone are perfectly fine.
My point being that without some reliable statistics pointing to springs being way more susceptible to wear than gold plated contact points, it doesn’t make any difference.
(FWIW: I currently work with factory equipment for PCB production testing and bad contact due to oxidation and wear is a much bigger issue than springs going bad, but that’s just my experience.)
I guess what we see is in part due to the transition towards more and more ”highlevel”. Now don’t get me wrong here, ”high level” in general is supposed to make life easier for developers, more rapid development and for corporate a better ROI. The downside is that it requires less understanding of the underlaying foundations (it hides it on purpose) from the developers/engineers.
Now I’m not saying that ”high level engineers” are less engineers than others, but it’s not surprising that we’re moving in the direction we’re moving. It’s by design.
(Now this doesn’t explain everything, far from it, but IMO it’s why we see an image writer weighting in on 300MB compared to a C/C++ version at <1MB)
That would put form over function , and would be dangerous. There is no reason to go "high level" just to convenience the engineers (except perhaps being able to hire cheaper, less qualified ones). The tradeoffs can be dangerous. Imagine this kind of fragility being installed in robocars.
Long story short:
Unexpected OpenSSL hard crashes in our application. Turns out our HW was reporting support for unaligned access where as it was actually disabled in CPU due to buggy hw (arm platform).
