Steven Sinofsky

On the PC side, Intel was so far behind that it just kept pulling both NVIDIA and ATI slash AMD to be, you know, what you used if you used Photoshop or made movies or were just graphic intensive.

And so in the next few weeks, we'll know what Apple is going to do for these APIs.

And more importantly, the models themselves and the runtime.

I mean, NVIDIA has an enormous investment in the open source models and tuning them through their hardware.

And the ecosystem has done a great job, as evidenced by the Mac minis, of tuning those APIs for the Mac.

But that has nothing to do with the phones.

And so that's an operating system difference.

And the number of phone people is large, and as we know, the hardware was the same.

Now, it's not quite the same, blah, blah, blah, amount of memory, all that stuff.

But it's very interesting to see the details of Microsoft and then what Apple chooses to do.

Well, certainly, having lived through like a half dozen component shortage things, you just sort of wait them out and you don't let some local Macs or local men determine the future.

This will all correct itself in short order.

The history of it, whether it's been DRAM or hard drives or processor shortage, all of these things, we've had them come and go, or even smaller components.

So I'm not worried about it at all.

I mean, obviously...

If you're thinking that you need 96 or 128 gig for a standard consumer device versus selling to eight on a MacBook Neo,

There's a huge difference.

But also that would change in the models too.

Like right now, the models themselves are all tuned to run in hyperscale data centers.

And every month, it seems like there's a new paper that says, oh, we cleaved this giant thing off of the inference pipeline.