3 ms·

Interesing article, I hadn't spent the time to follow the drama of these frameworks as we are still using AngularJS 1.X at work. I enjoy working with AngularJS

by iopuy 9y ago

Interesing article, I hadn't spent the time to follow the drama of these frameworks as we are still using AngularJS 1.X at work. I enjoy working with AngularJS and would be satisfied to build future projects with it. Will I be missing out if I choose to stick with an end-of-life framework that does everything I need or is it worth while to make the jump and invest the time to relearn something that I have already solved? Truly confused here.

rajangdavis 9y ago
I would still use Angular 1.* for certain projects, but I feel like it has to be the tool that works when nothing else will. I would take a look at React and Mithril. Mithril is pretty neat in that it's fast, lightweight, and everything's in javascript. I like that it is functional which totally changed how I approach Angular stuff. React is/was kind of hard for me to grok but it's not hard to get something going, just difficult to break certain habits coming from Angular.
slackingoff2017 9y ago
I learned React and Angular 2 at the same time during resume padding for a desperate job search :). Angular2 is a massive pile of needless shiny objects. On one hand, I LOVE Typescript to death. When you turn on all the strict compiler checks it's hard to write broken JavaScript for once. Combine it with TSLint and it has resulted in the first "nice" JavaScript development experience and codebase I've ever seen. That said, Typescript was the best thing about Angular2. When I figured out how to use it with React a lot of excitement faded away. A prime example... Angular2 has its own web client when Fetch polyfill is small and works great. All this needless complexity and replication of browser API's has bloated Angular codebase to the point that it's basically unusable without "AOT Compilation" which makes debugging hell and isn't compatible with a lot of libraries. What the web really needed was Typescript and a nice UI library. React + Typescript fulfills those needs. Most of Angular now has nothing to do with UI and IMO is needless bloat.

by iopuy 9y ago

rajangdavis 9y ago

I would still use Angular 1.* for certain projects, but I feel like it has to be the tool that works when nothing else will. I would take a look at React and Mithril. Mithril is pretty neat in that it's fast, lightweight, and everything's in javascript. I like that it is functional which totally changed how I approach Angular stuff. React is/was kind of hard for me to grok but it's not hard to get something going, just difficult to break certain habits coming from Angular.

slackingoff2017 9y ago

I learned React and Angular 2 at the same time during resume padding for a desperate job search :). Angular2 is a massive pile of needless shiny objects. On one hand, I LOVE Typescript to death. When you turn on all the strict compiler checks it's hard to write broken JavaScript for once. Combine it with TSLint and it has resulted in the first "nice" JavaScript development experience and codebase I've ever seen. That said, Typescript was the best thing about Angular2. When I figured out how to use it with React a lot of excitement faded away. A prime example... Angular2 has its own web client when Fetch polyfill is small and works great. All this needless complexity and replication of browser API's has bloated Angular codebase to the point that it's basically unusable without "AOT Compilation" which makes debugging hell and isn't compatible with a lot of libraries. What the web really needed was Typescript and a nice UI library. React + Typescript fulfills those needs. Most of Angular now has nothing to do with UI and IMO is needless bloat.