[message deleted]

Rewrote it to use a struct passed instead of referencing class properties, now massive fast. Still be nice to know for sure if my conjecture about runtime is true.

This would make sense if the objective-C runtime (or ARC) is still running on Intel, thus requiring a switch to Rosetta. If so, people should be made aware that any capture of self could cause a slowdown on M1. Odd if true, but I can't see how Apple could otherwise code such a simple concept so badly if it's native ARM.

I don't understand why Apple Engineers keep preferring Objective-C for sample code. I presume they think most people are still using it, but at my employer we converted to Swift years ago. Translating things mentally from Obj-C to Swift is now difficult because I haven't used it in years, and Swift is where most of the iOS/MacOS market is today. Back when I worked at Apple in the mid 90's we still had some sample code in Pascal, which made just as much sense, i.e. none. Maybe things will improve in WWDC 21.

I would suggest to Apple that it rewrite all the Metal examples in Swift instead of Objective-C which hardly anyone uses any more.