I don’t know why I waited so long to do so, but I’m glad I did. (:
Turns out not many major differences between the two. Was easy to switch.
Especially since Unity will be dropping support for JS in the future.
Before starting it feels like switching from English to French. But it turns out to be more like switching from American English to English English.
2 Likes
Exactly! _Sips tea as I write in British English_
2 Likes
Welcome to the Dark Side. We have generics.
2 Likes
There should be a Darker Dark Side. With C++ bindings and templates.
1 Like
And namespaces, getters/setters and cookies!
1 Like
Wait, I thought it was the web developers that had cookies… 
Don’t eat any cookies offered by web devs!
2 Likes
JavaScript isn’t bad. I use it a lot in my day job. (web development) But I will always prefer languages that have nice, strict typing. Being able to play fast and loose with variables is always too confusing for me. I like my types to stay what I initially declare them to be. This is why I always use C# with Unity. When I’m dealing with logic, I need some consistent structure. Willy-nilly just makes things harder to keep track of.
When I use JavaScript in my day job, I try to treat it like a more strictly typed language.
1 Like
I am all kinds of triggered.
On topic, nowadays I go “eww” if I see implementations of something I’m trying to figure out in JS.
Welcome to the club 
In case you are not aware of it, have you looked into TypeScript? Haven’t had a chance to play with it much myself, but it’s a javascript superset that imposes strict typing that ‘compiles’ to javascript.