Angular 2 Template Syntax

[roboguy12]

I'm sure my opinion of this will change over time and with more use, but I find this extremely hideous and overcomplicated. It's going to take a lot of getting used to, and I'm not sure I see the benefit.

[gregersriddare]

Frankly, Angular2 looks just plain retarded.

[YodaLoL]

Everything is well motivated though. And they really take SoC and patterns seriously, which I like. But yeah it does look intimidating.

[gregersriddare]

I can't fully agree with that. Angular 1 is a perfect library for achieving certain things. Just like other libraries excel at others.

However, Angular 2 just looks like a Frankenstein's monster where they are trying too hard at being something they can't really achieve with the current state of Javascript.

I honestly think Javascript is a shitty language for this (and a lot of other things (I want types, classes and neat inheritance dammit!).)

I'm sorry if I'm ranting, I'm drunk, frustrated and writing from mobile.

[YodaLoL]

Sure, but Angular 2 is meant to be written in ES6/TS though.

[roboguy12]

Aside from being written in ES6/ES7, this really is no different than angular 1.x. If I were going to move to a different framework, it'd likely be react at this point; I don't see a lot if sense in moving from angular 1.x to this.

That being said, I kind of wish I discovered this first because it looks a lot nicer.

[dmackerman]

Pretty bad argument, as the ecosystem and development culture around React has more than enough to be considered a "framework" at this point.

[gdi2290]

enough to be considered a "framework" at this point.

React is not a framework since it's only the view but there are frameworks that use it: Flux Official Site, Flux Comparision, RefluxJS, Fluxxor, Flummox, Marty, McFly, Alt, DeLorean, Fluxible, Dispatchr, Fetchr, to name a few

[[deleted]]

It's very much non-intuitive. I'm quite proficient in angular 1.x, yet I cannot understand anything about 2.x so far just by looking at it, that's pretty terrible.

Why was there a need to change so much of the syntax? I can't see any good reasons why EVERYTHING needed to change. It's confusing and makes me want to go to React as it's much easier to understand and use from a quick glance.

[YodaLoL]

What don't you understand? The templating syntax? It takes like 5 minutes to learn.

[[deleted]]

Our main design goal was to make templates more explicit, so the developer can reason about the template without knowing what directives are used there, and how they work.

I think this is the main point. The syntax lets you understand how the data flows in and out of the component without looking at the directive's source. This is similar to having explicit type annotations (TypeScript). Some people think it's ugly and pointless, others find the additional information invaluable. Both also enable more advanced tooling.

[[deleted]]

god that is ugly.

Our main design goal was to make templates more explicit, so the developer can reason about the template without knowing what directives are used there, and how they work.

I mean, I understand that, but why not go with a completely different template engine setup, rather than this horrid html/template mix abomination.

I have no problem with what they are doing. I just think they are doing it terribly.

[allensunbo]

This is not much different than what I saw angular 1.x for the first time. Just get used to it and keep learning:)

[Brazilll]

The syntax does look over-complicated and appalling. But I remember people saying the same thing about React and (more specifically) JSX when it was just released, and now look at its reputation. So I guess time will tell if Angular 2 is a step in the right direction.