Echo JS 0.11.0

I do not understand why some people continue to believe that the templating has no place client side. It reminds me of a past era where pages were fully reloaded just to show an error message.

I didnt know function parameters with default values were not counted in function length property. Why ? Who thought it would make sense ?

unnecessary _most of the time_, necessary sometimes. JavaScript on the server is still in its early days, maybe some future isomorphic solutions like Meteor will change the game. That's what I meant on point 8. 

I agree about flexibility, and the Angular team is listening. Check out Angular 2.0 goals : "For performance and to enable innovation, our goal is that almost every piece of AngularJS should be optional, replaceable, and even used in other non-AngularJS frameworks.  You’ll be able to pick and choose the parts you like and write or select others that you like better."

The level of logic to put in the DOM is debatable, we have full-logic solutions like EJS and logic-less like PURE, both approaches are valid depending on the project. If you think 2-way databinding is majority of time unnecessary, that means it is necessary sometimes, so why criticize Angular if it offers both ? And about things which are unnecessary majority of the time, you were talking of isomorphic ? Finally the refactor argument is not mine, I only reply to those used in the article.

Now what is wrong with this bullshit

1 - He basically said templating is not “real development”. Yet we use it since the early days of the web ! Doing the databinding on the JavaScript side is not easier, it is a real pain to get and maintain the right selectors. What do you think ? You’re not going to work on HTML, because you’re a “real developer” ? Dumb

2 - No it is not. User inputs are generally all specified and under control, so it is a precious time & code saver instead of plain old listeners. Also, every binding is optional & configurable on Angular

3 - Because he thinks a total abstraction of the DOM and diff calculation is faster and better for battery ? I'm not sure if he really knows how React works

4 - Of course you have to change the view and the controller if its a new feature ! What's wrong with that ? It is called separation of concerns, and a far better idea than putting everything in the same place

5 - Angular is fast enough to get really nice demos with Ionic on my lowcost smartphone. And Angular 2.0 will be even faster thanks to Object.observe. Also, what is the problem with HTML parsing ? That's the number one feature of every web browser

6 - Isomorphic websites is a nice concept to try to fix issues with obsolete browser support and JS-unaware crawling bots. Angular is made for _modern_ platforms

7 - The evening I started to learn Angular, I made a basic chat application and a tic tac toe game. When I learned Ember, it took me two days to make a recipe book application, and at the end my code was crap. Angular is excellent to quickly have working demos. I agree the next "industrial" step is quite more complicated.

8 - What is wrong is thinking that a single framework should be suitable for every web application in this world

9 - Open source ? Giant community ? Hello ?

10 - this complete refactor is a great thing for Angular and will make previous points even more inaccurate than they were already.

I'm not an "ngFanboy", I use Angular beside others (Backbone, Knockout <3). Sometimes I do not use any framework at all and it is fine.

If it's not hard, fork my lib and do it yourself :)

max-width: 930px; is not what I call fully responsive

"no need for HTML coding when building apps. Hire developers, not web coders :)" --> then i stop reading

need word-wrap: hyphens;