tgma

I am a fan of OLEDs and have enjoyed secondary PC laptops with OLED, however, to be clear:

- Most OLED PCs were not anywhere as bright as the old MBP miniLED display.

- Almost all OLED PCs have terrible blue shift when viewed at an angle.

- Apple miniLED XDR displays are no slouches either. They are not quite OLED, but they implemented the dimming zones very well with uniform backlighting and deep blacks.

I have not seen Apple's on MBP, but I bet it meets or exceeds iPad Pro Tandem OLED which does not have the two problems above.

So no, it is not the same as the decade old PC OLED. And I have ignored all the potential durability issues.

I would not assume it is software-locked. Display controller on 120Hz ProMotion displays is more expensive. Also, the panel itself is likely cheaper LTPS vs. LTPO.

Perhaps what allows Apple is to be better at certain things like that or security for average consumer is indeed at odds with some aspirations? At least in practice, not utopian dreams, that seems to be the case.

So you vote with your wallet for accessibility despite freedom and the rest of hacker news do the opposite and it all works itself out.

> Is it not obvious that not every global .com website owner wants to use only have the choice of US-run CAs

The major browsers are all US made though, so in the end there is an implicit trust on US vendors, even deeper than the trust on CA.

> It's also not at all a given that website owners would prefer the national CAs

The suggestion is to have a few major ones (LetsEncrypt) be able to sign everything like today but restrict the others. You can still choose to use the US one, just like you basically use CT logs from the US vendor today.

--

In practice, DNSSEC/DANE based solution may be the practical path forward along this line.

Personally? I'd agree with you. FWIW, you already have to trust your browser vendor, so you might as well trust Mozilla and Google and Apple and MSFT who can spin up one each, or collectively two or three CAs in US, UK, Switzerland, Ireland or sth like that.

That said, starting from the status quo, not sure that's the path of least resistance to get there.

Legacy CA/Browser Forum politics.

Also the industry has changed a lot since Let's Encrypt. You could have argued against monopolizing the CA issuance to just a few countries/entities as sovereignty issue, and CAs were indeed exhibiting extreme rent-seeking behavior before Let's Encrypt. With a guaranteed free and accessible alternative in the mix, the weight of the arguments against would change.

There is no valid reason my computer should come preloaded with 100+ trusted certificates from many jurisdictions that all can sign certs for all domains.

Only a few major CAs in jurisdictions that admit heavy scrutiny and legal liability should operate. Country-specific CAs, if any, should only be scoped to signing certificates for their respective ccTLDs.

Everything is relative, but fair enough.

I bet it would be the NVIDIA, at least initially, not for the encryption capability per se, but for simple fact that adapting to TPU at high performance is non-trivial.

I don't believe threat of litigation alone explains the extent of it.

The way an American company, esp a reputable one like Google, conducts itself internally is different. There will be much more internal backlash to do the wrong thing way before litigation.

America is a high-trust society.

Would be interesting to render a real desktop environment directly on top of that from the iPad. You'd get an OpenDarwin-like thing with the power of M4.

> ...sharing (and hence, phishing)

Sharing and phishing are on two different axes. You can have shareable credentials that are phishing-resistant when used.

You can have hardware-backed SSH keys that are not cloneable. You would need the browser to prevent phishing while still using SSH agent as its underlying signature mechanism (implied by my "in a consumer package").