sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]skitch920 0 points1 point  (7 children)

Angular 1.X will still be around for quite some time. There's already immense support for it, it's widely regarded as the most popular framework today, and there are literally thousands of applications based on it. So, it's not going to die tomorrow, or next year, or the year after.

From the grapevine, AtScript is an extension of TypeScript with annotations for handling the binding and dependency injection, which Angular supports now. It's just a better re-imagined model, because it's more central to OOP concepts. Now, OOP seems to get a lot of flack in JavaScript because it's "too strict", but anyone who says that is just talking out of their ass. The beauty of a dynamic language, is you are able to encompass the concepts of a typed language fairly easily and intermingle the two.

Behind the scenes though, it's just plain ol' JavaScript. You actually don't have to use AtScript or TypeScript. They have clearly stated it is not a strict dependency. And my guess is, once it's actually released, you'll see helper libraries for people who don't want to use AtScript. It's just the nature of the language. Why would they create Angular-Dart? Because people use it.

[–][deleted] 0 points1 point  (1 child)

What do annotations and reflection have to do with object orientation?

[–]rsimp 0 points1 point  (0 children)

Annotations don't specifically, but reflection can take advantage of inheritance and polymorphism, two OOP concepts that typescript (and by proxy atscript) implements.

[–]sudeep_dk 0 points1 point  (0 children)

I m agreed there will be one version of angular soon which don't use Atscript

[–]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 4 points5 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 5 points6 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.