> I can't escape the impression that they didn't really shower the wider ecosystem in DTKs and support, although I'd be happy to proven wrong there.
That’s interesting. I was shocked at how many green check marks there are for a chip that was announced in June. It takes time to write and test an application. A lot of teams must’ve really prioritized it.
Also, Apple Silicon compatibility is not enough. One needs Big Sur compatibility too.
I don't think the chip's announcement time really should go into anyone's consideration time here, since it's Apple's own choice to go for these timelines and release a "Pro" product in November :)
I mean this point is largely moot by Rosetta covering all the basics well and still making the Macbook Pro 13 a serviceable Pro computer for a lot of (but not all) use cases. It just seems strange to me that popular developer things like Go, Rust, Docker, virtualization of any kind are still months away despite these being super important use cases of the Mac. Maybe Apple just doesn't feel that way, or have the numbers showing that my impression isn't true, but it feels strange that they're letting the community just figure it out by themselves now.
Is this really a knock on Apple though? It’s not like all this is up to them. Personally I want MATLAB support but Apple doesn’t get to dictate Mathworks schedule.
That’s interesting. I was shocked at how many green check marks there are for a chip that was announced in June. It takes time to write and test an application. A lot of teams must’ve really prioritized it.
Also, Apple Silicon compatibility is not enough. One needs Big Sur compatibility too.