2 ms·
> 3. Idea of `(events)` and `[attributes]` is awesome, works really effective and makes code much more easy to read. This is encouraging. I always thought that
by Kiro 10y ago
> 3. Idea of `(events)` and `[attributes]` is awesome, works really effective and makes code much more easy to read.
This is encouraging. I always thought that looked aweful so it's nice to hear that it actually makes sense.
- eranation 10y agoWell it's a bit confusing / weird at first until you get used to it but the real confusing syntax is the mix of both for bidirectional binding, e.g. [(ngModel)], but after reading the docs it kinds of makes sense. Awesome job, love it so far.
- tiziano88 10y agoHaving used ng2 in production for a while, I personally dislike the model behind this, mainly because it is not actually symmetric as it appears from a first look: - input: ``` <foo [x]="y"></foo> ``` - output: ``` <foo (x)="y = $event"></foo> ``` To me this seems unfinished and inelegant; note also that everything is inherently mutable, but change detection will work best when the bound input values are reassigned, but if they are instead mutated at some deeper level, Angular will have trouble tracking those changes, and may behave in weird ways, which are often tricky to debug.
- EugeneOZ 10y agotry [()]