I've noticed that in the latest versions of C#, using classes isn't always required, which is pretty interesting. However, in Unity, it seems like you still have to use them. Is this because Unity is using an older C# version or is there another reason why classes are a must in Unity?
2 Answers
Game engines like Unity utilize classes for game objects in order to inherit from specific base classes. For instance, in Unity, if you create your own class, it has to inherit from GameObject, which allows it to function within the engine's framework. This is more about how Unity is structured rather than it using an older C# version.
C# hasn't eliminated classes; they've just made them optional in certain situations. Previously, you always needed a class for things like your main function, but now you can do that without one. However, you still need classes for many purposes, especially in Unity, which relies heavily on them for managing data structures and game mechanics.
I get what you're saying, but my main point is that while C# allows for other programming styles, Unity makes classes essential. I'm curious what specifically makes Unity-dependent on classes compared to general C# usage.