Oh, one very important thing I forgot to mention: why, at least on elf/linux, c++ is extremely toxic for game development, mainly because of gcc devs.
As I said, game binaries should "libdl" everything, namely be pure and simple ELF64 binaries (with the least amount of relocation _types_).
Well, the gcc standard c++ library just does not allow to do that at all, period. It does not have a "libdl" mode, and even worse, it seems it has hard dependencies into glibc internals.
The only mitigation is to maximize libdl-ization of the game binaries and to use a VERY VERY old set of glibc libs (cf what godot does, at a cost of kludge), because, the libstdc++ will be bound to (symbol/version)s of this set of glibc libs.
Comments
Oh, one very important thing I forgot to mention: why, at least on elf/linux, c++ is extremely toxic for game development, mainly because of gcc devs.
As I said, game binaries should "libdl" everything, namely be pure and simple ELF64 binaries (with the least amount of relocation _types_).
Well, the gcc standard c++ library just does not allow to do that at all, period. It does not have a "libdl" mode, and even worse, it seems it has hard dependencies into glibc internals.
The only mitigation is to maximize libdl-ization of the game binaries and to use a VERY VERY old set of glibc libs (cf what godot does, at a cost of kludge), because, the libstdc++ will be bound to (symbol/version)s of this set of glibc libs.