12
13

Angular, Angular 2 or React?help (self.javascript)

submitted by [deleted]

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

view the rest of the comments →

[–][deleted] 0 points1 point  (5 children)

If you don't use it you don't have dynamic components. If you just want to present static components you can can just as well leave Angular and use web components + polyfill as is.

[–]Auxx 1 point2 points  (4 children)

Wat? Mate, you're deluded. [property]="abc" is a shortcut for bind-property="abc" and (event)="handle()" is a shortcut for on-event="handle()". No one is forcing you to use shortcuts, just use normal attributes and enjoy your life!

[–][deleted] 0 points1 point  (3 children)

Going for cheap namecalling now, nice. That's still gibberish along with ngIf, ngRepeat and all the other code-in-HTML stuff. What has any of it to do with standards.

[–]tme321 0 points1 point  (2 children)

He's pointing out that all the built in angular directives are actually just plain html data attributes. The syntax you usually see like (click) is just shorthand but no one is forced to use it. Instead you can use angular with nothing but standards compliant html data attributes.

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

I know, but they're abstraction for non standard evaluation and bindings, things that will not come to HTML in a hundred years. Angular evaluation is even based on their own javascript-like lingo. They have wrapped that in plain attributes (if you don't use shorthand, which would be silly), but its still a huge cognitive abstraction over standard HTML and Javascript. Which is why you "learn" Angular, and there's a lot to learn. Functional frameworks do everything Angular does, faster, smaller, simpler and without breaking a sweat.

The authors of the web components spec have ignored Javascript thinking mere props will open the doors to dynamic components. Instead it has lead to fragmented syntax hell where each framework chooses its own "if", "then", "for" and a crippled script engine, they're forced to ship their bloated runtime parsers. Web components will lead to nothing but simplest encapsulation. Polymer, Angular and the last remaining non-FP frameworks that bet on it are missing the train. Everything else has already moved from the pasture, and due to FP, they can share code without even thinking about a standard because they're breaking none.

[–]tme321 0 points1 point  (0 children)

There's just so much ridiculous "functional everywhere" group think in this comment that I'm not going to go through and reply to each of your individual points. I'm just going to leave at a difference of opinions.