1. GDScript performance limits push developers to offload heavy work to C++/Rust via GDExtension
- “Was playing arround recently building an RTS with godot until i just hit the ceilling of what i could handle with gdscript performance wise. Than started to move alot of heavy logic to c++ simulation : tedious indeed but the results speak for themself. Basically allows me to use godot for things like menus dialogues and similar stuff while running the true heavy work in a c++ simulation.” – voodooEntity
- “gdscript is incredibly slow, worst than something like lua, maybe only good for handling the UI events.” – momocowcow
- “If you know rust, the Godot rust bindings for GDExtension are also really good and let you use any Rust library in Godot (including tokio and async rust if you really want).” – valorzard
2. Linux distribution and ABI compatibility challenges (versioning scripts, static linking)
- “Just don't forget the versioning script needed on at least Linux. It's either that or build with the same older distro Godot uses, so you have a matching libstdc++ version.” – fwsgonzo
- “Static linking libstdc++ with -fvisibility=hidden saved me on Linux, though it bit me the day I needed exceptions to cross the boundary.” – hnacobsxph
- “Basically, game binaries should be '-static-libgcc -static-libstdc++ --enable-new-dtags' everywhere, statically load ONLY common glibc libs (and with 'old' symbol versions…) and dynamically load everything else.” – sylware
3. Expanding ecosystem of language bindings (Rust, C#) and trade‑offs between GDExtension, engine modules, and linking strategies
- “Came here to mention this. As an example there's godot-iroh which uses iroh for peer to peer networking.” – aquariusDue
- “For C# there’s basically nothing in engine, so you’d use Rider or Superluminal.” – Fraterkes
- “.NET integration has the issue it doesn't work in all target platforms, that is why Capcom and Unity have their own compilers to native code.” – pjmlp