gdnim VS gdnative

Another option is Nim. Looks and writes like Python but closer to C in performance. It also has static typing so I prefer it for scripting as well.

People have built a few games with the Nim Godot bindings:

https://github.com/pragmagic/godot-nim

There’s also an interesting project to do hot reloading using dlls:

https://github.com/geekrelief/gdnim

I've been down this road. I forked godot-nim to https://github.com/geekrelief/gdnim and have add several features. I've since moved on to working on https://github.com/geekrelief/tm-nim, a binding for The Machinery.

I maintain a fork of the godot-nim binding https://github.com/geekrelief/gdnim/ All your issues I've dealt with by not relying on the godot editor. Instead I do all the setup with my build script which can generate the gdnlib, gdns, and tscn file for a node with script attached.

This is my first exposure to this and the proposal. I maintain a fork of godot-nim, https://github.com/geekrelief/gdnim. I know someone who was trying to exchange data between gdscript and godot-nim. Nim has a generic vector type: seq[T], and he was trying to expose that to gdscript. I told him to use an Array of Variants instead. Would this PR allow us to expose data structures from gdnative (or whatever) to gdscript?

I can't speak to the issues with setting things up. I never had a problem on Windows. But if you need help create an issue on the godot-nim repo someone might come along and help. I know at least one person that uses/used a mac to get godot-nim running. On my own repo, https://github.com/geekrelief/gdnim I plan to get osx working, but it's not my main dev machine.

It's a little less standard use, but Godot has been used to build application guis, which could be paired with rust bindings to implement app logic. I can't speak to reproducibility/scalability, but Godot's ui is extremely solid, and I'd probably choose that over Bevy until Bevy's ui progress matures.

Adding onto this, I successfully written a game in Godot using gdnative / gdext. I started with a split approach using gdscript and rust for CPU intensive but found that the API layer was slow at transferring large amounts of data (serialization?). I ended up rewriting it in all rust and it worked like a charm. I was able to target native and web assembly, the web assembly was much slower but worked on the browser.

Check this: https://github.com/tomuxmon/bevy_roguelike if you are still into bevy. Scheduling is a bit bork and I have not found time to port it to latest bevy. But most of the systems should work fine(if used on latest bevy). But again. If you want faster result go with something like Godot. In fact, just go with Godot. It is mature, easy to start, no lock in(free and MIT license), a lot of learning material. Also with Godot you can also use Rust https://godot-rust.github.io/. Ditch Unity (do not have time to explain 😅). Have fun!

Bevy Godot-Rust

> Same for Godot.

While likely true that it's "Unlikely to ever be as supported" as the 4 officially supported languages[0] ("GDScript, C#, and, via its GDExtension technology, C and C++."), Godot's GDExtension technology is specifically intended for use in adding support for other languages.

The most relevant tracking issue for Rust is presumably:

* <https://github.com/godot-rust/gdnative/issues/824>

Which links to:

* <https://github.com/godot-rust/gdextension>

[0] https://docs.godotengine.org/en/4.0/getting_started/step_by_...

...Godot v3.x has Rust support via godot-rust and Godot v4.0 is released as of this month?

I was curious, and looked it up. Nothing built in, but there's an interesting project that works with godot: https://godot-rust.github.io/

There's people working on it: https://godot-rust.github.io/