3 ms·
Because it’s terrible.
by adamnemecek 3y ago
Because it’s terrible.
- satvikpendem 3y agoBut it's the integrated approach you're talking about, what is terrible about Angular?
- adamnemecek 3y agoI just checked it’s so much worse than I remember <div *ngFor="let product of products"> <h3> {{ product.name }} </h3> </div>
- satvikpendem 3y agoAnd that is why I use React instead.
- adamnemecek 3y agoNot integrated enough for me.
- satvikpendem 3y agoIf you want something that's not "libraries on libraries," use Angular. And if you don't like Angular, you have proved my point, that the "integrated approach" is simply not good, because you cannot make your own decisions to improve parts you don't like. Hence why I said I use React and not Angular.
- adamnemecek 3y agoOr angular does it wrong?
- rabindranat 3y agoMaybe the "terrible" part you are referring to is rxjs. If so, signals should make things easier.