One of the most common criticisms of Angular 1.x is the potentially inefficient change detection algorithm tied to the digest cycle. In this post we will discuss some of the major improvements to change detection in Angular 2.0.
In this blog entry, author Geertjan Wielenga, wants to attempt to put together a simple Angular scenario where the relevance of TypeScript is shown, while using NetBeans IDE 8.1.
There is a myth that wants transclusion to be a hard concept to understand and manage, according to Angular.js. So, for today, we’ll wear the hat of Mythbusters, by displaying several simple examples of transclusion in Angular.js.
We previously shared part 1 of Dave's Angular testing series in this newsletter. He is now on the third part in this series. In the previous 2 articles (Part 1: Karma Setup and Part 2: Jasmine Syntax), Dave set the stage.
You aren’t writing tests for your Angular app. The code base is growing and you’re feeling more apprehensive each passing day. You’d like to start testing, but where do you start? In this article we’ll look at recipes that you can apply for testing the various components in your app: the services, controllers, and directives.
In his previous post, Aviv showed us how easy it can be to add your first Angular 2 service to an existing Angular 1 app, using ES5. This lets you easily have Angular 1 code live alongside Angular 2 code. This time, he’s helping us dip our toes in the real deal: adding our first component.
This article is for developers who are familiar with Angular 1.x and would like to learn more about React. We’ll look at the different approaches they take to building rich web applications, the overlapping functionality and the gaps that React doesn’t attempt to fill.