That’s because people are writing applications rather than documents with this stuff.

That’s because people are writing applications rather than documents with this stuff. The separation between markup and code (which makes sense for static documents) has been bogus for some time in web apps. If you’re not mixing HTML with JavaScript in JSX then you’re using some kind of domain specific language in your markup (ng-if, ng-repeat etc.) in AngularJS.

Originally shared by Xah Lee

This is worth mulling. Need complete analysis. What went wrong? or was it stupid hacker advice to begin with? #JavaScript

A series of five articles introducing Vue.

A series of five articles introducing Vue. If you are an Angular 1.0 developer and considering a move to Angular 2.0, you might consider stepping off that train and picking up Vue instead. Performance wise it’s a lot like React but philosophically it shares a lot with Angular 1.0 (but with a lot less of the bad stuff, i.e. less kruft and bad decisions).

One of my favorite things about Vue is that it takes all of the successful things from other frameworks, and incorporates them without getting disorganized. Some examples that stand out for me:

A virtual DOM with reactive components that offer the View layer only, props and a Redux-like store similar to React.

Conditional rendering, and services, similar to Angular.

Inspired by Polymer in part in terms of simplicity and performance, Vue offers a similar development style as HTML, styles, and JavaScript are composed in tandem.

Some benefits I’ve enjoyed over Vue’s competitors: cleaner, more semantic API offerings, slightly better performance than React, no use of polyfills like Polymer, and an isolated, less opinionated view than Angular, which is an MVC.

Putting Redux state management into an Angular 1.

Putting Redux state management into an Angular 1.0 app. This would go even better if the app scrapped using directives in favour of “components” which are a recent addition to Angular 1.0.

With Redux handling the business logic and by relegating Angular to the position of “view provider” this would make the process of migrating to Angular 2.0 easier (or for that matter, migrating to something else entirely such as: Vue, React, Aurelia etc.)