Angular 2, Google’s framework for building mobile and web apps in HTML and JavaScript, is now in beta. Link
Angular 2.0 Beta just came out and decided I post it here, since there seem to be alot Angular fans.
This means alot of us will have to jump to TypeScript to really enjoy the framework, and TypeScript isn’t really that bad, the question is are you willing to jump ship to TypeScript because of Angular 2 ?
It took me like forever trying to get along with angular before I dropped it. React was easier for me to get along with.
As regards Angular 2, I learnt its totally different from the previous version of Angular which presents challenges like compatibility and further learning curve. If this is true do you think it might affect its adoption?
Yes it’s totally different and in a good way, Angular 2.0 embraces JavaScript and when i say this i mean, using common module loaders, and also using other libraries. now Unlike Angular 1x , Angular 2 doesn’t fire a digest in every function, Angular will always be adopted, it’s a freaking popular framework.
I tried React and decided it was not for me, I don’t like the concept of template inside code, but VueJS is what I use now pending I migrate to Angular 2.0 for work.
But i can tell you this, Angular 2 learning curve is way lower than 1 because Angular 2 is more component centric something like React in some ways rather than the concept of Controllers, building web applications in sub-components is much more preferable, its what we do in VueJS and it’s easier to reuse modules in other projects.
I think being different is a huge problem here.
We have a product built with Angular/laravel. If we are going to migrate to Angular 2, it will be a huge task rewriting the whole app.
Now trust me there are a lot of people like us who already have their entire code base in Angular 1. Maybe there is a way out of this but looking at it from the surface, it is a convoluted situation.
Just like Python 2 and Python 3, the two stable versions of Angular will be maintained differently. This means you don’t necessarily have to migrate. But if you wish to start a new project, you can adopt Angular 2. But slow down, UI frameworks and other Angular dependent frameworks are still powered by version 1. So, chill till second quarter of 2016.
You’re not just putting templates inside code. That’s trivial.
You’re putting your view’s entire dependency graph into code and centralizing the state determining the output.
This means every possible view of your app can be represented as a single json object.
This is important because it means you can now think of React rendering your app as a function that you give structured data and get a structured result reliably. You don’t even need to be in the browser to get the correct result.
This is different from a template system because a template doesn’t guarantee to be what the views look like in production. Your template system provides the base html for the rest of your app to use.
In other words, with a template system, your app’s true state is the html. With React, your app’s state is a data structure.
Not exactly. There is a topic and it has been totally derailed by superfluous subjectivity, rather than the wealth of stuff that can be discussed on the subject matter itself. Typescript and its nitty-gritty for instance, ES7 and the future of Javascript, etc.
Meteor shouldn’t be compaied to Angular. Angular can be compared with Blaze (Meteor’s own frontend framework) but I guess there wouldn’t be any need for that since Meteor 1.2 now has an official support for Angular 1. For Meteor, its Angular, React or Blaze.
I don’t do NodeJS Web application only CLI which Go has replaced for me anyway, infact I’d rather go with Go “no pun intended” for web development why so, Go feels richer and one thing i hate about the Nodejs community is the ridiculous amount of node_modules dependencies each node_modules requires for a module.