The next topic I was struggling with is the nuances of the way data-binding is done in Angular-2 and how it is mapped to what I know from AngularJs (Aka Angular-1).
There is a tone of content about it. But at least to me it was a bit messy. There is also a huge amount of Q&A in stackoverflow with reports that data-binding do not work for different users (see this and this and this as examples). I guess I am not alone…
Here is the good news. I found the following blog as the cleanest overview of the Angular-2 data-binging and how it is mapped to the familiar Angular-1 directives.
Introduction to data binding in Angular 2 versus Angular 1
Thank you Siebe Hiemstra. This one helped me!
For the past couple of weeks I’ve been drowning in huge amount of new information, trying to self-learn with the help of my fellow developers what is Angular2 and how to build modern NodeJS+Angular2 projects.
Well the process is not easy. There are tones of write-ups and tones of opinions. New insights become obsolete in very short time and one can never be sure if what is written is even still applicable and if it is in any way best-practice.
I found myself a bit overwhelmed. I was not sure where/how to start this exciting journey.
Here are few things and data sources I’ve used so far:
Perhaps the first iteration that I had was with the Tour Of Heroes tutorial. While there are several things I would probably do differently now, IMHO this is still the best way to start.
The second thing that I was searching for is how to structure a project if you have backend APIs using Express and client side using Angular2. To tell you the truth that was not easy for me and what helped me was the MEAN App with Angular 2 tutorial. It is not perfect for what I need but it sure gave me an insight into some of the consideration on how to organize my project.
The next obstacle for me was the integration with Bootstrap. In AngularJS (or Angular 1) I used the Angular-UI package. The same team also delivers now Angular 2 support. However, I gave the ng2-bootstrap package a try and at least for me it did the work well and seems to be a bit more native to angular 2.
With these initial set of packages and tutorials I felt good enough to start to experiment with this brand new world of Angular 2. This is just the beginning. Stay tuned…
And here comes Angular2…
I’m now about to start a new project, all from scratch, and this project has both new constrains as well as new opportunities to continue to evolve the software stack.
On the database side there is a constraint to use Cassandra and that is probably a topic for a different writeup. On the client side, the team also wanted to naturally see what all the noise about Angular2 means (Angular2 arrives-Sep 2016).
We are just starting so this is all new to me and reflective the initial study and running tutorials only (Quick Start and Tour Of Heroes).
My first reaction is that Angular2 is simply a new animal. The known concepts from AngularJs did not smoothly move to the new framework. Also, the transition to Angular2 also requires (or at least recommend) to transition the development language to Typescript, that I do not know. Hence the removal of the Js from the name.
For me that means an unexpected disruption in my personal growth. Restarting the client side technology learning almost from the beginning. I suspect that this is true for many developers.
From a longer term perspective this is probably something good, the platform seems to have tons of promises for faster to load applications and better balance between server side and client side processing. I can imagine that in couple of years and additional releases, the platform will become a major platform. Mastering it early is probably something positive.
But on the immediate timeframe that is a real setback…