Live data from Hacker News

Dissecting the Apple M1 GPU, Part III

rosenzweig.io

11–20 of 131 posts

Re: Dissecting the Apple M1 GPU, Part III

#14
post #9

Very interesting analysis! > Simply put – Apple doesn’t need to care about Vulkan or OpenGL performance. Apple being Apple. They just can't play nice with standards.

This is the advantage of building your hardware and your software under the same roof. You can make optimizations (such as not including hardware that makes OpenGL faster, but doesn't impact Metal nearly as much.) The "standard" here is the Metal API, not the GPU hardware.

Re: Dissecting the Apple M1 GPU, Part III

#16
post #14
post #9

Very interesting analysis! > Simply put – Apple doesn’t need to care about Vulkan or OpenGL performance. Apple being Apple. They just can't play nice with standards.

This is the advantage of building your hardware and your software under the same roof. You can make optimizations (such as not including hardware that makes OpenGL faster, but doesn't impact Metal nearly as much.) The "standard" here is the Metal API, not the GPU hardware.

I don't think it's an advantage to sabotage the adoption of common API like Vulkan. It holds the progress back and I totally blame Apple for pointless NIH and lack of collaboration here.

Apple are doing it out of rather sickening lock-in culture in the company and Metal is far from the only example like that.

Re: Dissecting the Apple M1 GPU, Part III

#17

Unrelated - All this work is done by an 18 year old. Absolutely incredible. Some people are simply built differently and admittedly, it makes me jealous.

Something about this comment on each of Alyssa’s posts[1] rubs me the wrong way. I find her work remarkable even without the context of her age. Why mention it? Highlighting it is almost diminutive, even though I know that the comment is not intended to be that way.

[1] https://news.ycombinator.com/item?id=25875552

Re: Dissecting the Apple M1 GPU, Part III

#18
post #16
post #14

Earlier quoted context omitted.

This is the advantage of building your hardware and your software under the same roof. You can make optimizations (such as not including hardware that makes OpenGL faster, but doesn't impact Metal nearly as much.) The "standard" here is the Metal API, not the GPU hardware.

I don't think it's an advantage to sabotage the adoption of common API like Vulkan. It holds the progress back and I totally blame Apple for pointless NIH and lack of collaboration here. Apple are doing it out of rather sickening lock-in culture in the company and Metal is far from the only example like that.

Apple are doing it because there’s no benefit to them in doing it the way that you want them to.

Apple Pay the piper, and Apple call the tune. Whether you like it or not is immaterial.

Re: Dissecting the Apple M1 GPU, Part III

#19
post #16

Earlier quoted context omitted.

I don't think it's an advantage to sabotage the adoption of common API like Vulkan. It holds the progress back and I totally blame Apple for pointless NIH and lack of collaboration here. Apple are doing it out of rather sickening lock-in culture in the company and Metal is far from the only example like that.

Apple are doing it because there’s no benefit to them in doing it the way that you want them to. Apple Pay the piper, and Apple call the tune. Whether you like it or not is immaterial.

Apple has every right to do that as they control their stack. And people who favor FOSS projects have every right to criticize Apple for exercising their control in a way that adversely impacts FOSS.

Re: Dissecting the Apple M1 GPU, Part III

#20

Unrelated - All this work is done by an 18 year old. Absolutely incredible. Some people are simply built differently and admittedly, it makes me jealous.

Something about this comment on each of Alyssa’s posts[1] rubs me the wrong way. I find her work remarkable even without the context of her age. Why mention it? Highlighting it is almost diminutive, even though I know that the comment is not intended to be that way. [1] https://news.ycombinator.com/item?id=25875552

Because it’s interesting and intent matters. Maybe you’re being too sensitive, and too vicariously sensitive, about a fact that’s obviously stand-out interesting.
Post reply on HN