Sharing Top Content from the Angular-sphere.

Working on the Bleeding Edge

  • The “missing” 2 beta releases are the beta 4 and beta 5 which were declared as “incorrect” by Angular team straight after they were published and were replaced by beta 6 .
  • If you take out the first three weeks before the beta 1 (which was the first beta having any changes) was released, you get the average of 1 release per week.
  • Working on the Bleeding Edge – Building an Angular 2 Application During Beta Phase
  • I also share some advice on how to get through the beta successfully.
  • Angular 2 had just reached its first beta at that point.

Read the full article, click here.


@zinyando: “Working on the Bleeding Edge – Building an Angular 2 Application During Beta Phase #angular2 #angularjs”


Using a technology in a beta stage is often considered to be nerve-racking and time consuming as there are constant backward-incompatible changes and lots of bugs. Here’s what I observed while using Angular 2 during its beta phase. I also share some advice on how to get through the beta successfully.


Working on the Bleeding Edge

Comments are closed, but trackbacks and pingbacks are open.