October 3, 2016
Take 3, Scene 14: The Present and Future of Angular 2, Part 1
On this two-part episode of Take 3, Cassian Lup and Andrei Tamas join us all the way from Romania to discuss the newest iteration of the AngularJS framework: Angular 2. Angular 2 is a framework meant for both web and mobile app development.
- Cassian and Andrei share the background behind Angular 2 and how 2014 became the year of Angular
- We discuss how much Angular has changed from its first iteration, and Cassian and Andrei share how much they’ve worked with it
- Andrei and Cassian share some insight into why Angular was both hyped and feared during its release stage
About the Guests
Read the Transcription
Julia Slattery: So let’s start with a brief overview. What is Angular and how is it used?
But the new trend is we build the API that actually enables us to build a separate appliance and then the client with the API would communicate. And the client runs on the users’ device, be it a browser on a computer or a mobile device or a native device even. We can do that. But there’s this bridge that we need to build between the two. So the separate approach of having the API built separately from the client side is where Angular really shines. It’s the answer to building these apps in a very elegant way on the client side.
Andrei Tamas: Definitely. I agree with that; Angular was a big promoter of that one since the first day it arrived.
Julia Slattery: There have been two iterations of it – Angular 1 and now Angular 2. Can you speak to why Angular 1 completely took over the whole app development world, to the point where 2014 became the year of Angular 1?
Andrei Tamas: Definitely, I agree. Testing was a big, important addition and something that was truly made popular only with the rise of Angular apps actually. I’ve heard of that.
Julia Slattery: Angular 2 was recently released to the world. Have you both had a chance to work with it yet?
Cassian Lup: So I remember being at Angular Connect last year, which by the way is taking place these days in London. It’s probably the biggest event you could go to, to get your Angular fix. So the majority of the Google core team working on Angular is there. And they announced Angular 2 beta, right? So that was a major breakthrough, lots of applause, you know people were highly excited about that. You just saw the whole new different way of writing Angular apps. And people were both scared but confident on making this work.
So that was the first time I actually got my hands dirty with Angular 2, one year ago. And since then, I’ve been following the releases that took place. I went through several betas, and then through release candidates – as a matter of fact, they had six of them. And recently just launch the stable, official release that they encourage you to use in production. So I’ve been keeping an eye on that. Admittedly not on each release because there have been some breaking changes. There’s a lot of politics involved. They change their router completely. But yeah, you know mostly toying and experiencing with what writing Angular 2 apps is and feels like. There’s actually a super-secret initiative here in 3Pillar that we’re trying to work with to experience new technologies. And Angular 2 is part of our labs system where we go and build this internal app in Angular 2. So I’ll say that that’s the most serious and hands-on experience I do have with the framework.
Andrei Tamas: For myself, I’ve also kept a close eye on Angular 2 and its progress and evolution. Like Cassi, I think I first laid my hands on it early after last year’s Angular Connect conference and played a bit with the initial betas. After that, life got in the way and I had to drop it for a while. But recently, since the latest release candidates were launched and now that we have Angular 2, I’ve actually started to devise a plan on how to migrate my own big Angular app to Angular 2. And it’s quite an exciting process, and hopefully that will happen soon enough and I’ll be able to fully enjoy Angular 2 in my day-to-day work.