4 ms·

Well, I think Angular may be unintuitive for people having gotten used to the "jquery way" of thinking. But I think the jquery way of thinking is the problem he

by maaaats 13y ago

Well, I think Angular may be unintuitive for people having gotten used to the "jquery way" of thinking. But I think the jquery way of thinking is the problem here. For too long people have been doing direct DOM-manipulation, and fail to see how they can achieve what they want in a more declarative manner. When I started using Angular I had really no experience with jquery or any other js framework, and I felt Angular was intuitive.

kitsune_ 13y ago
Data binding coupled with a declarative syntax isn't a "new thing", especially in the enterprise world, .NET and Java. It's an acquired taste and I never really felt comfortable with it. You can build some perverse architectural monstrosities on top of it. Of course that's true for every technology or framework, but I am of the opinion that many of frameworks that tout data binding / declarative syntax actively encourage going into this direction. I'm somewhat surprised that it's so popular with the JS crowd right now.
- RyanZAG 13y ago
  There's a reason data binding is popular with the JS crowd, and it's the same reason it's been somewhat popular with the big enterprise crowd. When your application starts getting very complicated, such as the user changing an input field that is reflected in a bunch of dynamic calculations across the app, it becomes desirable to simply change one value and have everything update. This is only desirable if your application is big enough that it's not just easier to re-run every calculation manually. Big enterprise has had this problem for a long time in their big multi window monster apps they use for stock trading, etc. JS webapps have been very simple for a long time and haven't really needed it until recently. Now that they're getting complex, JS devs are looking into how to solve the problem and it generally comes down to MVC OOP style or FP style. You can see these two derivatives in AnglularJS and ReactiveJS.
- maaaats 13y ago
  You are right. I come from the backend world, so that may be the reason I felt jquery was "weird" and angular "right".

by maaaats 13y ago

kitsune_ 13y ago

Data binding coupled with a declarative syntax isn't a "new thing", especially in the enterprise world, .NET and Java. It's an acquired taste and I never really felt comfortable with it. You can build some perverse architectural monstrosities on top of it. Of course that's true for every technology or framework, but I am of the opinion that many of frameworks that tout data binding / declarative syntax actively encourage going into this direction. I'm somewhat surprised that it's so popular with the JS crowd right now.

RyanZAG 13y ago
There's a reason data binding is popular with the JS crowd, and it's the same reason it's been somewhat popular with the big enterprise crowd. When your application starts getting very complicated, such as the user changing an input field that is reflected in a bunch of dynamic calculations across the app, it becomes desirable to simply change one value and have everything update. This is only desirable if your application is big enough that it's not just easier to re-run every calculation manually. Big enterprise has had this problem for a long time in their big multi window monster apps they use for stock trading, etc. JS webapps have been very simple for a long time and haven't really needed it until recently. Now that they're getting complex, JS devs are looking into how to solve the problem and it generally comes down to MVC OOP style or FP style. You can see these two derivatives in AnglularJS and ReactiveJS.
maaaats 13y ago
You are right. I come from the backend world, so that may be the reason I felt jquery was "weird" and angular "right".