News for hackers. Stuff that matters.
Re:Dissecting the Apple M1 GPU, Part III by marcan_42 on Sunday April 18, 2021 @11:35PM (#26858913)
You're talking about macOS. We're talking about AGX2. If you want to complain about Apple's API support in macOS, a discussion about AGX2 support for Linux is not the right venue.

I am, quite honestly, getting very tired of all the off-topic gratuitous Apple bashing in articles about our Linux porting project.

Re:Dissecting the Apple M1 GPU, Part III by BolandJ on Monday April 19, 2021 @12:17AM (#26859052)
Shmerl pops up on every thread mentioning Vulkan/Apple spouting conspiracy theory nonsense that every design decision is some kind of evil plan to screw over open standards. Ignore him.

Keep up the great work, plenty of people really appreciate it.

Re:Dissecting the Apple M1 GPU, Part III by pjmlp on Monday April 19, 2021 @06:27AM (#26861072)
And keeps forgeting no one in the games industry, or console vendors for that matter, cares about his conspiracy theories.
Re:Dissecting the Apple M1 GPU, Part III by glaze on Monday April 19, 2021 @10:35AM (#26863181)
Yup, I doubt he has experience working in the games industry. Many engines support multiple graphics APIs and there's often only 1-2 employees implementing/maintaining them so speaking about vendor lock-in is not a strong argument.
Re:Dissecting the Apple M1 GPU, Part III by shmerl on Monday April 19, 2021 @12:34PM (#26864690)
How is that a counter argument to anything? The need to support multiple APIs is not free. It's a tax on everything else.
Re:Dissecting the Apple M1 GPU, Part III by glaze on Monday April 19, 2021 @12:39PM (#26864758)
You're right that it's not free. But compared to the whole game engine codebase size the renderer backend is usually not big.
Re:Dissecting the Apple M1 GPU, Part III by shmerl on Monday April 19, 2021 @05:03PM (#26867966)
It is a waste of time that could be avoided. And exists only becasue of insistence on lock-in by the likes of Apple.
Re:Dissecting the Apple M1 GPU, Part III by shmerl on Monday April 19, 2021 @10:15AM (#26862976)
Lock-in proponents bring their kool aid. Not impressed. Gaming industry is pretty messed up when it comes to lock-in. Everyone is paying this tax.
Re:Dissecting the Apple M1 GPU, Part III by pjmlp on Monday April 19, 2021 @10:55AM (#26863404)
I am aware of my limitations as human being in this society, speak from actual work experience, and will use any tooling that I rant about when it is on the best interests of the customers, regardless of my personal agenda.

Something to think about, or maybe not.

Re:Dissecting the Apple M1 GPU, Part III by mlindner on Monday April 19, 2021 @12:27AM (#26859101)
Yes I agree it's tiresome, I wish hacker news had rules against people making bad faith arguments more so than they do now.
[dead]
Re:Dissecting the Apple M1 GPU, Part III by marcan_42 on Monday April 19, 2021 @02:37AM (#26859698)
Your argument is equivalent to criticizing ARM for putting in instructions to optimize Javascript into their architecture, as if that "sabotages" every other programming language. Or Intel for putting in instructions to optimize AES into their architecture, as if that "sabotages" Salsa20.

It doesn't make any sense. Of course Apple optimizes Metal for their GPUs and their GPUs for Metal. None of that is hostile towards other APIs. All of this hardware is Turing-complete and by definition can implement any conceivable graphics API. The only question is how well it performs with those APIs, and until we have benchmark numbers, your argument is based on assumptions lacking any evidence.

Re:Dissecting the Apple M1 GPU, Part III by shmerl on Monday April 19, 2021 @03:38AM (#26860018)
I'm not sure what Turing completeness argument has to do with anything. Turing machine is also Turing complete. You are going to make GPUs like that.

We are talking about a simple fact - Apple don't care to collaborate on Vulkan, neither when designing their GPUs nor for their OS. I see no point to further argue about facts. And I see criticism of that as completely valid.

Re:Dissecting the Apple M1 GPU, Part III by glaze on Monday April 19, 2021 @10:30AM (#26863143)
Supporting both Vulkan and Metal in a game engine is not a huge task. I work in the games industry, my job is to implement and maintain graphics backends to a renderer engine, so I can speak from experience.
Re:Dissecting the Apple M1 GPU, Part III by shmerl on Monday April 19, 2021 @12:37PM (#26864724)
Huge or not, duplication of effort is a tax. And no, it's not trivial as you claim. Especially when some engine wasn't designed from the ground up to address these differences.
Re:Dissecting the Apple M1 GPU, Part III by pertymcpert on Monday April 19, 2021 @01:40AM (#26859394)
I think you haven't effectively countered their point.