Like many people, I’ve spent the last few days looking for the new Unity. Godot has some potential, especially if it can take advantage of an influx of dev talent to drive rapid improvement. Open source is cool like that. However, one major issue holds it back - the binding layer between engine code and gameplay code is structurally built to be slow in ways which are very hard to fix without tearing everything down and rebuilding the entire API from scratch.
    • OctorineEnglish
      3·
      1 year ago

      Are you sure this isn’t selection bias?

      Is it really that the the Godot approach is fast enough most of the time, or is it that everyone who needs perf has just decided to use something else.

    • Ferk@kbin.social
      1·
      1 year ago

      Thanks for the insight!
      I assume you are talking about compiling a GDExtension using C or some lower level language, right? not C#
      What I’m wondering is if it’d actually be more efficient to use C# than GDScript in Godot. Because I would have expected the opposite.

      • bram dingelstad :nb_flag:@gamedev.lgbt
        2·
        1 year ago

        @Ferk we’re using Rust with GDNative

        the reason not being performance, but language features (Rust makes it easy to have good safety guarantees)

        C# is overall more performant than GDScript, but it is rare that you get to use that performance in a way that it makes a measurable difference

        i always just tell people to work with what they know well and what makes them feel comfortable, thats the most important

        great part about godot: you can run these languages side by side ✨