this post was submitted on 17 Aug 2023
75 points (100.0% liked)
Godot
5851 readers
35 users here now
Welcome to the programming.dev Godot community!
This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.
Make sure to follow the Godot CoC while chatting
We have a matrix room that can be used for chatting with other members of the community here
Links
Other Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Rules
- Posts need to be in english
- Posts with explicit content must be tagged with nsfw
- We do not condone harassment inside the community as well as trolling or equivalent behaviour
- Do not post illegal materials or post things encouraging actions such as pirating games
We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent
Wormhole
Credits
- The icon is a modified version of the official godot engine logo (changing the colors to a gradient and black background)
- The banner is from Godot Design
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Those major Unity release versions are more comparable to Godot 3.x and 4.x
My point is that evidently minor releases of Godot are not sufficiently API stable, so that people feel the need to create and use a tool to switch between minor versions to work around compatibility issues. And I have seen some people complain about exactly that with Godot.
This has been a problem since forever with Godot. They like to backport major new features from the development branch to a new minor version of the previous branch. This means the API in the previous branch (3.x right now) is supposedly stable in that it is only extended and not modified. However there are two problems with this:
If you use the new extended API is makes the project bound to that version and you lost backward compatibility. So it becomes the responsibility of the user to keep track of which feature are available in which versions and be conscious of backwards compatibility, instead of just sticking with a major version like you can with basically every other software in existence.
It's not even true. They modify the existing API and break projects all the time. The movement functions of the kinematic body classes have been changed at least three times during the 3.x cycle.
So you're right, the API is not stable, but you won't get far with criticism from a professional software standpoint in the community (have a look at the demographics listed in the recent community poll for some insight as to why).
Ultimately because of the relative instability of the API, I think this tool will be useful.