Maybe you should look a few things up before jumping in.
> Why is this author flaming Angular.JS?
If you are a proponent of it and you think you are defending it here, you might actually be doing it a bit of disservice.
He made the point that Angular JS is complex and showed a list of new concepts it introduces -- services, directives, etc on top of the already existing ones, controllers and so on. It is a personal opinion. You don't think it is complex, ok, share your opinion, it doesn't mean the author if "flaming" anything.
> They both try to solve the hardship of having to update your DOM, via an abstraction that only works well in specific circumstances
They both solve a similar problem with some differences. Author thinks one does a better job sometimes.
> . But even more often a bad developer blames the platform for their own inability to architect their app cleanly and thinks leaky abstractions are the answer.
Are you implying the author is a bad developer? Can you show that. So far you haven't
How is it a non-sequitur? Random Code sample? Are you being a little too aggressive maybe.
> DOM programming is inherently "reactive" - it's event based.
I don't think you quite know what reactive means.
http://en.wikipedia.org/wiki/Reactive_programming
Maybe you should look a few things up before jumping in.
> Why is this author flaming Angular.JS?
If you are a proponent of it and you think you are defending it here, you might actually be doing it a bit of disservice.
He made the point that Angular JS is complex and showed a list of new concepts it introduces -- services, directives, etc on top of the already existing ones, controllers and so on. It is a personal opinion. You don't think it is complex, ok, share your opinion, it doesn't mean the author if "flaming" anything.
> They both try to solve the hardship of having to update your DOM, via an abstraction that only works well in specific circumstances
They both solve a similar problem with some differences. Author thinks one does a better job sometimes.
> . But even more often a bad developer blames the platform for their own inability to architect their app cleanly and thinks leaky abstractions are the answer.
Are you implying the author is a bad developer? Can you show that. So far you haven't