- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
I made a blog post about my experience switching from Unity to Godot earlier this year, and some tips for Unity devs.
I made a blog post about my experience switching from Unity to Godot earlier this year, and some tips for Unity devs.
I’m sure you’re right, and it looks serviceable. It’s not really about that, though. I’ve done the “learn a new language” thing many, many times. It gets old and I’m sort of over it - it’s not as fun as it once was, particularly now I have my favorite that I know well and am good at.
GDScript works almost 1-1 like Python. Any experience with Python almost instantly translates into knowing what to do in GDSCript, but not necessarily the other way around, as their script has a couple more builtin features.
Was going to say this but you beat me to it: if you know Python, you pretty much already know GDScript. It’s not at all like needing to learn another language from scratch.
If you’ve done it a lot then you know how easy it is to get up and running with a new language.
Really, it’s not that hard. GDscript is not some archaic clunker like COBOL with outdated paradigms, nor some esoteric joke language like Brainfuck that’s just pointlessly difficult. You’re going to be fine with it inside of a day.