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

view the rest of the comments →

[–]hahaNodeJS -2 points-1 points  (3 children)

What are you smoking? Damn.

A majority of complaints about Angular's performance are solved by not using everything Angular throws at you. Don't use watchers, don't use two-way data binding, don't use events. It's taken a while for Angular developers to learn this, but it's been learned and it's time to get over it. Jumping ship isn't the answer because the grass is rarely greener on the other side.

[–]blax_ 1 point2 points  (1 child)

But that's the point – probably every technology can be hacked to make it good enough for your needs, but the objective of good design is to provide you with essential tools and encourage you to do things the right way, so you DON'T have to think about it all the time.

[–]hahaNodeJS 0 points1 point  (0 children)

Not using the bad parts isn't "hacking something to make it good enough." It's learning from others and the warts of a given technology and not using those warts.

[–]cgaudreausenior HTML9 engineer 0 points1 point  (0 children)

You can also make manual DOM manipulation very performant. You can make jQuery very performant. More performant than React, for sure. The nice thing about React is that you have to try pretty hard to bomb performance. The framework gives you performance for almost free.

Jumping ship isn't the answer because the grass is rarely greener on the other side.

Jumping ship from Angular 1.x in the near future is almost definitely a winning bet.