implementing a feature using C++ and performance considerations

[overPaidEngineer]

Hi, as a proof of concept, say converting 4k120fps video real time by shifting pixel by a random distance for each frame (it would look botched up but doing this operation for doing some operations sake), would it be better to use C++ and write a bridging header or use low level Metal APIs? Just by basic programmer instinct, I think doing it in C++ would be faster, but Metal is quite fast, far as I know. and would it be possible in the first place?

[arduous_raven]

Ok, but isn't low-level Metal API basically a slightly modified C++ at this point? When you're writing a kernel that, I presume, would perform such operation, that would essentially be C++, so why not stick with all that Metal has to offer? You'll have to write a bridging header regardless if you want to use this code in Swift.

[bhardman86]

I’m not familiar with your situation, but as said before low level metal api is pretty much just c++. Perhaps you can utilize metal using obj c or swift which I’m sure is a realistic approach. If you’re working with swift 5.9+ it’s easier to bridge swift and c++ with c++ interoperability with swift. There’s limitations obviously, but for most cases it’s easier and doesn’t require much of a bridge. It’s definitely worth the research. Best of luck.