On: Porting my JavaScript game engine to C for no reas...

[0cf8612b2e1e]

Huh. Never would have guessed. I am sure there were many “fancy” effects in the game, but during my playthrough, it all felt like it would have been achievable on a SNES.

[Kiro → 0cf8612b2e1e]

It's not about that. They are talking about complications in general when porting a JavaScript game to Switch.

See https://news.ycombinator.com/item?id=41155807

[pjmlp → Kiro]

That is to be expected by anything that isn't C, C++ and Assembly, also why Unity has IL2CPP.

Even Rust is going to be heroic levels until console vendors decide it is an acceptable language to be made available on their devkits.

[jdnxudbe → pjmlp]

I am not familiar with either Rust or the Switch, so maybe you can enlighten me: why would a Rust game be challenging on the Switch?

As long as you have a good C ffi (which Rust has), shouldn't it be quite easy?

Or is the Switch more similar to Android/iPhone where you cannot (could not?) run native code directly but have to use a platform specific language like Java or Objective C?

[flohofwoe → jdnxudbe]

AFAIK some (all?) console vendors require you to use the compiler toolchain from their SDK to compile your code. So unless the console SDK includes a Rust toolchain the only way is to somehow translate the Rust code to C or C++ and compile that with the SDK compiler.

Maybe if the console SDK toolchain is Clang based it would also work to go via LLVM bitcode instead of C/C++ though.

[pjmlp → jdnxudbe]

As flohofwoe pointed out, you are limited by the console vendor SDK, the compiler toolchains, and everything required to target their OS, linker, API, ABI,...