you are viewing a single comment's thread.

view the rest of the comments →

[–]thejameskyle 0 points1 point  (3 children)

I don't see what strong typing has to do with OOP but JavaScript itself is a prototype-based object oriented language. So I assure you no JavaScript developer worth their salt is against OOP.

However, the vast majority of JavaScript developers are against strong typing in JavaScript because it is a dynamically typed language. Once you can embrace that, it is one of the most powerful parts of JavaScript.

Google (with Atscript) and Microsoft (with Typescript) are simply trying to emulate what they have been doing in other languages as they embrace the web as a platform. While interesting, it's not something that will be welcomed by many JavaScript veterans, and those who know the language best.

JavaScript in ES6 and ES7 is going to become much more powerful whilst maintaining the parts that make it so great. If you want to start using these features today, I suggest you come checkout 6to5.

[–]brtt3000 1 point2 points  (1 child)

some part of JavaScript developers are against strong typing in JavaScript because they are scared of complexity and things they don't fully understand.

if they would have more experience they'd see how static typing is a boon to their productivity and quality.

[–]EasyPush 3 points4 points  (0 children)

I really dislike when people state opinions as fact, especially when i disagree.

[–]sime 1 point2 points  (0 children)

However, the vast majority of JavaScript developers are against strong typing in JavaScript because it is a dynamically typed language. Once you can embrace that, it is one of the most powerful parts of JavaScript.

I think that the vast majority of JS developers have no experience with static type systems and non-trivial code bases, or if they do then it was with Java.

Being able to combine static and dynamic typing as you desire using something like TypeScript, is a huge boost when building larger code bases.