The anatomy of a Godot API call
sampruden.github.io
The anatomy of a Godot API call
1–10 of 195 posts
Re: The anatomy of a Godot API call
#2How usable is Godot's native/C++ API for actual game programming, akin to Unreal? (never mind the hot reloading).
Re: The anatomy of a Godot API call
#3Sounds a lot like Unity to me.
Re: The anatomy of a Godot API call
#4I'm not sure I understood everything here, but I think the tl;dr is that Godot has a powerful new rendering technique called "foreshadowing".
Re: The anatomy of a Godot API call
#5The thesis of the article appears to be
> 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.
If there is one thing I've learned from the prevalence of Java, or JavaScript, is that performance problems will get sorted out fairly quickly if people start flocking to a tool.
Re: The anatomy of a Godot API call
#6This matches up with what I've heard from people with experience in both Unity and Godot. As convenient as it would be if Godot was ready to swap in for Unity, it's got some significant issues that would make that difficult to unfeasible for many people.
Re: The anatomy of a Godot API call
#7The thesis of the article appears to be > 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. If there is one thing I've learned from the prevalence of Java, or JavaScript, is that performance problems will get sorted out fairly qu…
Javascript still remains slow.
Java is fast enough that it doesn't matter.
However, no one will use Java to build Linux kernel.
Re: The anatomy of a Godot API call
#8I'm not sure I understood everything here, but I think the tl;dr is that Godot has a powerful new rendering technique called "foreshadowing".
cue theatrical thunder and lightning
Re: The anatomy of a Godot API call
#9The thesis of the article appears to be > 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. If there is one thing I've learned from the prevalence of Java, or JavaScript, is that performance problems will get sorted out fairly qu…
[deleted]
Re: The anatomy of a Godot API call
#10The thesis of the article appears to be > 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. If there is one thing I've learned from the prevalence of Java, or JavaScript, is that performance problems will get sorted out fairly qu…
Javascript still remains slow. Java is fast enough that it doesn't matter. However, no one will use Java to build Linux kernel.
JavaScript isn't slow