1) I'm not sure if that is directed at me but I am trying to be helpful. If you have a specific question or are confused about something, just ask. I will try to answer as best I can. I do agree that sometimes false information can be helpful, but I'm not sure this is one of those cases.
2) Yes, everyone has different experiences and a different perspective. I did not read the whole tutorial, maybe they explain themselves better later, and I'll give them the benefit of the doubt. I don't need to contact them. They can write whatever they want on their own website, it doesn't bother me that much.
3) You are correct. There are a lot of unanswered questions on the forum. It seems like sometimes people try the engine and have a problem and maybe just quit since they are not finding help. Or there are more complex questions that no one here knows (expect maybe the engine developers). I don't know, I just got here not long ago. Hopefully if people stick around we can grow the community.
Yes, other engines have used nodes. OGRE in specific was based on a node system like Godot and the object was called Node, same as Godot. There are also many engines based on a scene graph, which is a related structure to nodes (but in a more limited sense). Even in Unity, you can have parent and child objects (so if you scale the parent, both objects change). This is basic functionality for most engines/frameworks (even if they have different names).
4) I think you are getting bogged down in the terminology. It doesn't matter what the class is called (whether Node or GameObject or whatever). Just start working in Godot and you will quickly see how it works. If you are not already familiar with game development, some things may be confusing at first. This is normal and fine. But the real way to learn is to just get working. Try to make a Pong clone or something simple and see how it goes. Cheers.
