73
Introducing Godots: Ultimate go-to hub for managing your Godot versions and projects! (programming.dev)
submitted 3 years ago by to c/godot@programming.dev
25 comments fedilink hide all child comments
 

Nice app I saw shared

Source: https://github.com/MakovWait/godots

Download Links (Win, Macos, Linux): https://github.com/MakovWait/godots/releases/tag/v1.0.stable

you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 3 years ago* (2 children)

Godot 4.x projects are compatible with each other and are stable but some people don't upgrade right away for stability or plugins specific to that version. You don't see many companies upgrading from Unity 2021 straight into Unity 2022 when it drops, they'd still use Unity 2021 for various reasons. That's why Unity has Unity Hub for managing versions. I think a project like this can be useful.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago

    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:

    1. 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.

    2. 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.

  • permalink
  • fedilink
  • source
  • parent