Anyone making a claim that trust will be 0% based on a single thing is obviously oversimplifying the situation. Trust is built on behavior, reputation, time, repeatability, etc.
Trust is subjective and relative.
If Alice doesn’t trust Eve, that doesn’t automatically mean that Bob doesn’t trust Eve. That usually requires both Alice and Bob to similar experiences or Bob must have a trust relationship with Alice.
Trust also changes over time. One CEO change and a company can change overnight thus causing all trust to evaporate. Normally CEOs are aware of this and don't change things and so trust transfers, but one mistake and you lose trust. It takes a lot to build back trust, but a few years of proving worthy of trust and it starts to come back. If your competitors violates trust in the mean time customers are more likely to risk you, and if you prove trustworthy the customers are likely to stay.
There are other factors than trust as well - the US government really wants intel fabs to take off and they may be applying pressure that we are not aware of. It could well be that Apple is willing to risk Intel because the US government will buy a lot of macs/iphones but only if they CPU is made in the US. (this would be a smart thing for the US todo for geopolitical reasons)
Some random person I met dropped their phone in a river, just after arriving in a foreign country. He bought a new phone, but getting back to his phone number was not easy or possible for him (while in a foreign country). If he had an eSIM it would have quickly solved the problem for him. Instead he had to wait until he got home to pop in a new SIM card.
I learned from this experience that maybe eSIM is a good idea and I switched immediately upon hearing this person's story. Did I miss something?
I should have clarified that he dropped the phone in the river AND he did not attempt to get it back from the river, thus the SIM card is considered lost as well :)
> If he had an eSIM it would have quickly solved the problem for him.
Except many carriers have you jump through hoops to activate an eSIM on a new device. Here in the comments one person has to receive a new QR over snail mail.
FWIW, I dropped my phone in the Chicago River. Crossing a drawbridge, I pulled out my phone to check the time. It slipped and fell - right into the gap in the middle. I peered through the gap to see if was there, and was able to see the splash it made.
Neither SIM nor eSIM would have helped.
In that case, I waited to get home (I didn't live in Illinois) and got a new SIM by mail.
> in a foreign country [...] If he had an eSIM it would have quickly solved the problem for him. Instead he had to wait until he got home to pop in a new SIM card.
Are you sure that his carrier allows activating an eSIM while roaming? Mine definitely doesn't, which means that if I break my phone while abroad, I lose access to online banking.
Funny how everyone shits on Nvidia's monopoly when we've got Google walking around after winning a monumental antitrust case regarding their Android/Chrome/Google information monopoly.
> Funny how everyone shits on Nvidia's monopoly when we've got Google walking around after winning a monumental antitrust case regarding their Android/Chrome/Google information monopoly.
... are you implying people around here don't give google flak for monopolistic business practices? That doesn't square with my experience, here.
Not in most cases. Apple, AMD, and most other chip makers lack a fab. The design what the fabs can make, but they don't have much input into the fabs. Someone makes a fab, and you make something it can made.
Of course things are never that neat. I have no doubt the large players have input into the fabs - we have no idea what. However the two teams are still different companies, when the fab and chip design are the same company there is the possibility of more cooperation (or less - we don't know. In the best case for both there is more when it is all internal, but we don't know if this is the best case)
> This is actually based on "The Kernel in The Mind" by Moon Hee Lee.
This looks like a really interesting resource. Can anybody here vouch for its accuracy or usefulness? I can't find a ton about it online. The fact that it's only published as a series of LinkedIn posts, or a PDF attached to a LinkedIn post, does not fill me with confidence - but I guess we can't expect kernel devs to know how to create websites?
reply