I agree. It’s interesting, but I never thought of 64 bit only leading to higher quality code.
You'd be surprised. It's more an issue of resourcing. Do you keep investing and maintaining the 32-bit compatibility, or let it go? At some point, a growing support matrix starts to take on exponential growth of resources required to keep it going. Microsoft in particular seems okay paying those costs, but it also has not added nearly the level of libraries to Windows that Apple has to macOS/iOS. MapKit, AVFoundation, etc, etc. Win32 as an API has practically been frozen since the 90s. And their efforts to get folks on 64-bit have been lukewarm at best.
A concrete example though is Carbon. It is 32-bit only, and has been facing code rot for years now, but they technically have to support it as long as apps use it. But by phasing out 32-bit, they also get to phase out a 20-year-old API that was there mostly to help devs transition code from macOS 9.
AMD is the king of computing since now. Get used to this, guys.
Intel will not have anything faster than AMD for foreseeable Future means, that at best - we will have a tie between them.
While I like my Ryzen 3xxx system, AMD's biggest enemy at this point is themselves, IMO. The engineers there are doing good work, but are under-resourced to handle the sort of scale Intel currently operates at, IMO. The non-trivial microcode bugs (boost/power in particular) that took months to iron out aren't a great sign that they have the tools required to oust Intel from the majority of the install base. And that's ignoring the manufacturing scale difference between the two, where AMD would rely almost entirely on TMSC to be able to grow shipment numbers.
AMD is also not in a position of strength for laptops, at the moment. They need to get their laptop hardware into better shape on the Zen 2 or later architecture to realistically compete in the same way they've demonstrated for desktop and up.
While it will take time for Intel to have a response, they still have quite a bit of time. It will take quite a long time to grow and erode Intel's market share. EYPC is supposed to help AMD hit 10% market share in servers in 2020. That means Intel will still be taking home nearly 10 times the sales in the server space, despite having a "less advanced" product. That money, and the time it takes for AMD to grow in servers and laptops, in particular, gives Intel the "high ground" in a sense, despite having a less compelling product in the shorter term.
If it appears in Apple kexts, and it is semi-custom product it means two things:
1) Apple is testing stuff on this hardware, because they already have samples of it. That is what they need Kexts in the OS for.
2) APPLE ORDERED THE DESIGN OF VAN GOGH! Nobody else could, and it wont appear anywhere else, if it is product for Apple, for which, everything points to. You get it right now, what Van Gogh is, and what is happening?
I will admit that if Apple
isn't looking at AMD parts at this point, they are looking at a
possible repeat of the G5 fiasco. And the good news is that AMD at least doesn't require another architecture shift to support. Honestly, I think where this thing shows up depends a lot on what Van Gogh
is.
AMD's APUs historically been budget parts. So going by that, the Air or 13" MBP are likely targets. Looking at the Ryzen 7 APU available in the Surface Laptop (a Zen+ part), it'd have to be a Zen 2 part to even think about using it in the 16" MBP refresh due to the performance gap (not likely due to timing).
The exciting possibility is a Zen 2 APU built on desktop Ryzen 7 aimed at the Mac Mini, IMO. But that would be something new for AMD, which does align with the "semi-custom". Something in the 3700 class with an integrated GPU would let Apple go to 8 cores with SMT on the Mini without changing the chassis, and use something 3600 class for the cheaper model.
What I meant was this: you can build a AMD Based system that will be faster than fully loaded Mac Pro, for the price of the basic model.
TBH, you can do the same with Intel parts if you aren't paying out the nose for Xeon-class hardware. That said, you do at least get ECC with Threadripper vs Intel's HEDT parts.