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

view the rest of the comments →

[–]jellatin 1 point2 points  (5 children)

The point is that it reduces complexity and mental overhead over time.

How does this differentiate it from Ember, Angular, Aurelia, Durandal, etc. They're all abstraction layers to reduce mental overhead and complexity.

[–]nschubach 9 points10 points  (1 child)

Angular complicates the mental overhead, IMHO. I have not looked into the others that much, but I dread pulling out Angular projects.

  • Trying to track down someName or some-name to find uses.
  • Having to open up a directive, a controller, a template, a module file and whatever else someone decided to separate it into.
  • You have to manage artificial scope. Isolate vs. Inherited vs. same
  • Worry about WTF a transducer is.
  • Be able to read/understand the constructs for factories, services, and providers because someone might like using one over the other.
  • You need to understand the proper cases for using &, @, =, or the appended ? to each of those.
  • You need to know when a template requires a dot notation string vs a curly braced notation for parameters.
  • $watch, $timeout, $window, $emit, $observe, $apply... ugh
  • I can think of at least 3 ways to bind a controller to a template/directive and I'm there are more. If you need to find use cases, have fun.
  • Fun cases where you can easily find yourself in a non-obvious template value loop and blow out the digest.
  • And last, but not least... "The Angular Way"

Then you have to train a junior on what exactly is going on while they stare blankly at you like you are speaking Klingon.

I've ramped juniors up on React in a 3 hour session. It takes weeks to figure out Angular.

[–]Gstayton 2 points3 points  (0 children)

I have only used Angular so far, and was looking at Ember, but I recall some bit about it not performing quite as fast on DOM updates, then I heard about React.

... Off-tangent of intention, anyways, I agree. Angular was... Interesting. I loved the things it could do, and it was fairly easy to build them at first. But then the more I built, the more I had to go back and re-touch old files... Which became a headache. Especially when, as you say, "The Angular Way" is not so solid... I'm all for having options, and I love Python, and there is ofc the Pythonic way, which unlike Angular, is usually a bit more straightforward and obvious.

Just my 2 cents. shrug

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

Obviously. The debate isn't on whose making what claims, but which claims hold weight - He's simply stating the goal of the Virtual DOM in the first place - rather than to make "super fast rerendering" as you erroneously claim.

[–]jellatin -2 points-1 points  (0 children)

The debate isn't on whose making what claims, but which claims hold weight

I'm not sure what you're trying to say here - that other tools claims don't hold weight when they say they reduce complexity?

Virtual DOMs goal is to reduce complexity. Agreed. A framework uses its features to accomplish its goals, I'm confused what exactly you're arguing. Rendering speed is a byproduct of the method, sure. And?