3 ms·
> but it means you also miss out on whatever package manager comes with the language. I didn't even consider that! Good call out! > Similar to above, GDScrip
by giancarlostoro 4y ago
> but it means you also miss out on whatever package manager comes with the language.
I didn't even consider that! Good call out!
> Similar to above, GDScript and a lot of areas of the engine feel more strongly orientated towards fast and easy dev time rather than game performance.
Correct me if I'm wrong or way off, but isn't GDNative (or whatever it might be called now) basically for those moments where you need a little more beef, but don't want to rebuild the entire engine, so you bring in Rust or D or any other language you know and love and bridge it in through GDNative?
- bodge5000 4y agoYeh so the bindings with GDNative do absolutely help performance, and I imagine Rust with Godot would be even faster than Unity with C# (You can also use GDNative to add ECS as well I believe), but out the box, and therefore likely the direction Godot is heading in, seems to favour workflow above performance. That being said, it could be a "grass is greener" issue. There are plenty of engines that offer better performance but a worse workflow, Unity for one, that I'm not using and instead using Godot, and I guess bindings are as close as reasonably feasible to getting the best of both worlds, so I cant complain much.