-
Notifications
You must be signed in to change notification settings - Fork 114
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
32 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
--- | ||
layout: default | ||
title: Learn Angular 2 | ||
--- | ||
|
||
![Angular2](https://angular.io/resources/images/logos/standard/shield-large.png) | ||
|
||
Angular 2 is the next version of Google's massively popular MV* framework for building complex | ||
applications in the browser (and beyond). | ||
|
||
When Angular 2 was announced in October 2014 at the ngEurope conference, the ngCommunity was up in arms: what did this mean for their favorite | ||
framework they invested so much time into learning and building real things with? A lot of Angular developers | ||
were worried that Angular 2 would spell the end for Angular. | ||
|
||
Few teams are as invested in Angular as the [Ionic SDK](http://ionicframework.com/) team is. We've spent | ||
years building our entire business on Angular. When Angular 2 was announced, we were also concerned that the next version of our favorite framework would negatively impact us. | ||
|
||
What we found when we started building with Angular 2, though, was something beyond our wildest dreams: a faster, more powerful, cleaner, and easier to use tool than we had with Angular 1. We found a tool that embraced future web standards and brought ES6 to more developers around the world. | ||
|
||
We realized that Angular 2 would make it *easier* to use Ionic, not harder. That it would give us performance gains | ||
we desperately needed to push forward our goal of making the web win on mobile. That it would make it easier to write clean, testable code that would run on more devices and platforms. That it would help us empower more web developers to build great mobile apps. | ||
|
||
We knew we had to work to make sure the ngCommunity transitioned from Angular 1 to Angular 2 as quickly and cleanly as possible, so we started this site to help with the transition. | ||
|
||
As Angular 2 moves from alpha to beta and beyond, we will be updating this site with new tutorials and examples. If you ever have a question or feel there is something we could expand, [tweet at us](http://twitter.com/ionicframework). | ||
|
||
We hope you find Angular 2 as inspiring as we have, and we hope this guide helps you get there as quickly as possible. | ||
|
||
Cheers!<br> | ||
*[Max Lynch](http://twitter.com/maxlynch)*<br> | ||
*Co-creator of Ionic*<br> | ||
*May 2015* |