... these is true about the Godot game engine, see this video from the DanDoesDev - the official youtube channel.
The recal ai comes with these result:
Summary of Issues and Their Accuracy
No Bulk Copy or Export of Errors
Godot does not provide a built-in way to copy multiple errors at once or export them to a file, which can be inconvenient for developers.
This limitation exists in stable versions. However, error logs are saved in log files, which can be used as a workaround 00:01:00
No Set Data Type in GDScript
GDScript lacks a native set type, forcing users to use dictionaries or arrays to represent collections without duplicates, which is less intuitive.
This is a real limitation in stable releases 00:02:00
AnimationPlayer Issues
Function calls in AnimationPlayer are referenced by name, so renaming functions breaks animations.
Parameters must be manually specified, making the system fragile and error-prone.
Duplicated resources are not unique by default, requiring manual "make unique" steps to avoid unintended shared changes.
These problems are present in stable versions and affect daily use 00:03:00
GDScript Type System Limitations
No support for nested types or interfaces, limiting code robustness and scalability.
Dictionary methods do not infer types automatically, requiring explicit type declarations that can lead to errors.
These limitations exist in stable versions 00:05:00
Node Type Confusion
Nodes have two types: one from the scene hierarchy and one from the attached script, which can cause scripts to access non-existent properties, leading to fragile code.
This is a real issue in stable Godot versions 00:06:00
3D Asset Import Creates Extra Scene Node
Imported 3D models come as a scene with a root Node3D containing the mesh, making access to the mesh less direct and somewhat clunky.
This usability issue is present in stable versions 