I wonder if they do bin them though, just not for iPhones or iPads. Perhaps today's A13/A14s that have small defects are tomorrow's Apple TV or HomePod CPUs.

That would make them incredibly overpowered, wouldn't it?

A quick look in ifixit's HomePod teardown (2018) reveals an Apple A8 processor, last seen in the iPhone 6 (released 2014): https://www.ifixit.com/Teardown/HomePod+Teardown/103133

I wonder how long they manufacture their processor lines for.

Apple TV might get it; those devices usually processors that are within a few years of their flagships'.

I've had good luck with VMware Fusion.

WMware is the only kext that I've seen to cause kernel panic on a Mac.

I drive a 2013 FRS (older US version of the 86) and I'll experience weird dropouts all day like once every couple of months. Otherwise it works flawlessly. Very strange. You might try using it now and again and see if the problem "just goes away". Very frustrating though. I did not opt for the touchscreen however. I think my head unit is made by Pioneer.

There's a fascinating write-up by John Carmack in there about porting the original Wolfenstein 3D to the iPhone. Crazy to think that was over 10 years ago.

https://github.com/videogamepreservation/wolf3dios/blob/mast...

Terminator does as well.

I would. Both because it's more idiomatic and because it's inevitable more functions will be added.

You might be interested in Boost.Outcome (v2) or the proposed std::expected.

It's called the C++ REST SDK (https://github.com/Microsoft/cpprestsdk) now and is fairly active. I've used it client-side and I've really enjoyed it.

Thanks for taking the time to type this up. Having just written a class similar to Span in C++ I was curious as to how this would be accomplished in C#.

I'd say for strings it's entirely ___domain dependent. Many problem ___domain's won't ever use `std::variant` but may require that all strings live in ROM, so for those domains the default behavior makes perfect sense. If you want to compare C++ to modern languages, I get it, it's obtuse, but C++ is also used in instances where other languages can't be and so has to at least support doing things that may be unintuitive in other domains. That being said it would be nice if we could deprecate things with wholly better replacements like raw pointers, raw arrays, etc.