44 ms·

Angular 2 Final Released

838 points by mikeryan52 10y ago

Yhippa 10y ago
Front end development is crazy these days. I remember on my road to learning Java EE banging my head on the wall trying to put together things like dependency management with Maven, ORM's, and all sorts of arcane concepts and patterns. It took me a long time to get to that point but now it seems all too familiar. As someone coming up to speed with frameworks like React and Angular 2 it feels like that all over again.
- crypto5 10y ago
  I think in angular everything is already tied together, and you just write code.
- jacobsenscott 10y ago
  That's Conway's law for you. All three frameworks were built by meglogcorp, and they all feel exactly the same. It is funny that after the Rails driven success web devs had moving away from J2EE they are falling right back into the same traps - ultra complex bloated frameworks built on a terrible language.
  - arahaya 10y ago
    Symfony comes to mind. It's like a php clone of Spring.
  - indexerror 10y ago
    > ultra complex bloated frameworks built on a terrible language Even if you consider JS a bad language, proper abstractions can change the face of it entirely. By your logic, assembly is also bad since it is absurd to write anything useful in it. IMO Elm is a step in the right direction.
    - axihack 10y ago
      I've been doing a lot of FE for many years now and have worked with all major frameworks and I love JS and its flexibility. That being said I think we've been building one framework after another trying to abstract the things that make JS a language not suitable for state dependent apps. Elm feels like the right step compared to anything else out there.
  - choward 10y ago
    Javascript is definitely a terrible language, but it is the only language for the web unless you consider languages that transpile to javascript. Are you suggesting not using a javascript framework, using a transpiled language instead of javascript, not writing any front end code at all, or doing something ridiculous like turbolinks?
    - bezzi 10y ago
      What is wrong with turbo links???
    - calsy 10y ago
      Why would you consider JS to be a terrible language? It's not a requirement to use a framework to code in JS.
      - jomamaxx 10y ago
        "Why would you consider JS to be a terrible language? " JS is kind of a 'bad language' because: 1) It's missing some pretty important things. Try to determine if a value is a number. Seriously. Look into that mess. Or anything else. Doing simple type-checking is crazy, and we basically are resigned to 'best practices' - which is crazy. 2) Prototype chaining is a neat idea and has some merits - but in reality it makes things super-duper complicated. Ask 10 JS devs how it works and get 21 answers. That is bad. 3) Almost nothing is built in. You need to use a lot of 3rd party libs to do common things. 4) There is no such thing as 'JS' - ever browser, every version - you get completely different implementations. Maybe we can't blame 'JS' - but pragmatically, this means JS is a problem. A minor issue is issues with packaging, encapsulation and scale, which is also a function of loose typing. When JS programs get complex, they get unruly, and you wish you might be able to do things in an OO language at that point. JS is really light, and that has advantages - and I think it's the best language for a lot of async things - and UI's are inherently async - so that's good. In 5-8 years JS might be 'stabilized' in terms of libs or de-facto standards and it will grow. To anyone who's programmed in other, more established languages, I think it's clear JS has some weirdness that doesn't need to be there. But I like it.
- freyr 10y ago
  That's funny; as someone familiar with React, Angular, etc., the Java ecosystem seems utterly impenetrable.
  - dfsegoat 10y ago
    Yeah - we consult with an angular + Java group (for angular only) --- I can't understand half of what they are talking about when they talk about Enterprise level Java web projects. Java for Hadoop, Spark etc I work with daily.
    - eitally 10y ago
      Enterprise projects tend to have way more convoluted business logic and interfaces than consumer stuff -- it doesn't get nearly the love it deserves imho. Those developers, DBAs, devops folks, and sysadmins suffer sooooo much every day.
      - waltero 10y ago
        absolutely - but typically you can't get all this pain across to the 'business' because of an enormous lack of understanding. As long as the buttons in the GUI look nice and shiny, who cares what happens further under the hood..
      - j_jochem 10y ago
        Java EE is basically an excuse for consultants to overcharge for overengineering solutions to problems that were already complex to begin with. Source: Did some Java EE consulting here and there.
    - deleted 10y ago
      [deleted]
- eternalban 10y ago
  I venture a guess that you learned JEE by rote and not from first principles. Learning by rote is stressful since your mind has to retain effectively a bag of (to it incomprehensible) technical trivia. In contrast, first principles are compact and generative, and such a grasp also informs your intuition so you can actually make educated guesses and jump in the deep end when picking up a new stack. Same principles apply to learning programming languages. The biggest headache in picking new stacks today is the current trend of technical neologisms, so a bit of initial squinting (for recognition) is required.
- szines 10y ago
  If you use Ember.js, which is the most matured and serious on the market, you never had that feeling that JS changes a lot. Consistent and continuous improvement. The best choice.
- dlandis 10y ago
  That's very true -- it is reminiscent of the old J2EE days 12+ years ago. But it didn't really take long back then for a consensus to emerge about how awful most of that technology was (enterprise java beans, etc) and for people to settle on more simplified, streamlined approaches. How long will it take for the momentum in the front end community to similarly shift away from these bloatware approaches?
  - iamcreasy 10y ago
    I am a java programmer and I want to head towards web development. My first thought was learning JSP, Servlet and then move towards different frameworks like Spring. I don't know much - but can you tell me why JavaEE is an awful technology?
joshschreuder 10y ago
There's more info on future plans here: https://angularjs.blogspot.com.au/2016/09/angular2-final.html https://angularjs.blogspot.com.au/2016/09/angular2-final.htm... Specifically: > Bug fixes and non-breaking features for APIs marked as stable > More guides and live examples specific to your use cases > More work on animations > Angular Material 2 > Moving WebWorkers out of experimental > More features and more languages for Angular Universal > Even more speed and payload size improvements And immediately: > Semantic Versioning
- Lx1oG-AWb6h_ZG0 10y ago
  Ha! I foolishly thought that when ng2 hit RC, it actually meant things would be stable. Keeping up with the ridiculous amount of breaking changes (the router, for example) through the RC versions was a horrible experience.
  - xeromal 10y ago
    Hahaha. No shit. Stackoverflow would be like "You are using the wrong router. Use version x." Then someone said "No, version x is deprecated as of last night. Use version z. They skipped y after abandoning that too."
chrisballinger 10y ago
I expected angular.io to be a flashy example Angular 2 SPA and was disappointed when I realized it was just a regular old static HTML website. I guess most of the content is more suited for a static site. At least the search bar on the docs page looks like it has some Angular going on. Also it would be neat if the docs had dynamic examples instead of screenshots.
- borplk 10y ago
  Same. I think it would be a nice statement to make if angular.io itself was an Angular app that was a joy to use.
- unknowingone 10y ago
  But can it compete with this? https://react-bootstrap.github.io/components.html https://react-bootstrap.github.io/components.html
  - Bahamut 10y ago
    I think ultimately ng-bootstrap* (https://ng-bootstrap.github.io/ https://ng-bootstrap.github.io/) will be better, but I'm biased. API signature looks much better than shoehorning everything into components that don't belong there - we have a lot of work to go though, so it currently is still a work in progress. * I am a part of the UI Bootstrap/ng-bootstrap team - we worked on ng-bootstrap starting back in last August/September and have the benefit of two of our team members currently working on the Angular team.
    - winstonewert 10y ago
      Could you elaborate on what you mean by "shoehorning everything into components that don't belong there"?
      - Bahamut 10y ago
        There seems to be a lot of advocacy for tossing everything into the component tree in the React ecosystem - recently I got linked to a snide remark by Ryan Florence on Twitter implicitly arguing for putting everything in the component tree, including constructs that should have a better separation such as routing (which the tweet appeared to be a reference to). Some services don't belong in JSX though - this is why you have the idea of stores in Flux/Redux/etc. Some data doesn't make sense to couple to the component hierarchy - doing so makes it very easy to create dependencies on the component tree, which decreases modularity, as well as has perf ramifications by increasing the DOM elements that get rendered unnecessarily by React. Some examples are data models, routing, and interactions with non-element DOM api (window.location, XHR, etc.). This also has a side-effect of increasing difficulty of testing what generally should be vanilla constructs not tied to various frameworks/libraries unnecessarily.
stevehiehn 10y ago
Yes!!, I was starting to get nervous I jumped the gun using it at work!
gkoberger 10y ago
As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.
- deleted 10y ago
  [deleted]
- Pfhreak 10y ago
  As someone who uses React currently, this would be useful to me too.
- irrational 10y ago
  Or Vue.js, or Inferno, or...
- asher_ 10y ago
  I'm currently in the same boat. Both are similar in that they are component-oriented. There are two important factors in my mind. 1. The ecosystem (as you mentioned). React has a clear head start here, but I expect Angular2 to make some gains over time. 2. Angular2 gives you a full framework, and as they say now, a whole platform. React is smaller and you rely on a bunch of other packages to get all the extra features you need. If you want a full solution, Angular2 gives you that. This can be argued as a good thing or a bad thing. More flexibility with React, but also more things you need to figure out and make a decision about. With Angular2, once you buy in, you don't need to make all of those decisions. In my particular circumstance, which is to migrate an Angular1 app to a newer framework over time (mainly for the server side rendering features), Angular2 provides a clearer path and offers some nifty features like component styles that allow a similar migration with CSS.
  - BigJono 10y ago
    As someone who has never used Angular but is interested in Angular 2, can you give some examples of the framework-y things it provides that React doesn't? Redux is really the only thing I find necessary for what I've developed so far, and I'm sure Angular has it's equivalent, but what else does it have?
mshenfield 10y ago
Found this pretty helpful in grasping differences between angular 1 and 2. https://angular.io/docs/ts/latest/cookbook/a1-a2-quick-reference.html https://angular.io/docs/ts/latest/cookbook/a1-a2-quick-refer...
wcarss 10y ago
Is there a definitive angular versus react versus ember (or others) pros/cons/community status page out there somewhere?
- dfsegoat 10y ago
  Remember though, Angular is an (opinionated) framework, react is a lightweight library.
  - Nemcue 10y ago
    I wish people would just stop pointing this out. While technically true when people refer to React they're referring to the canonical stack that people use (i.e. + Redux).
    - ng12 10y ago
      I don't think that makes a difference. I can take a scalpel to my Redux code without really worrying about how it affects my React code. This is why I use React + Redux with some Webpack magic -- everything is encapsulated and composable from the ground up.
- Grangar 10y ago
  Not definitive, but there are a lot of good comparisons: http://smashingboxes.com/blog/choosing-a-front-end-framework-angular-ember-react http://smashingboxes.com/blog/choosing-a-front-end-framework... https://www.developereconomics.com/feature-comparison-of-4-popular-js-mv-frameworks https://www.developereconomics.com/feature-comparison-of-4-p... https://www.developereconomics.com/comparison-4-popular-javascript-mv-frameworks-part-2 https://www.developereconomics.com/comparison-4-popular-java...
- swalsh 10y ago
  You know what, these religious debates need a war to settle the question. Let's get 3 of the best teams for each stack, have them build the same 4 apps that cover a few of the most common scenarios... and let's see who's solution is done the fastest, is most maintainable, and has the best performance.
meltbuzz 10y ago
nice
xuwupeng2000 10y ago
I am on the boat of Angular 1. I really want to move to React cuz I don't want to learn TypecScript.
- eyelidlessness 10y ago
  FWIW you already know TypeScript, it's a superset of JavaScript (though you'll get few benefits from that).
- alxhub 10y ago
  Even if you use React, you should try Typescript. Totally worth it.
  - morsmodr 10y ago
    +1 Billion minimum for this comment
- dfsegoat 10y ago
  I was really frightened with it. But webstorm from jetbrains has an EAP version which basically shows your compiled JS file "nested" under your typescript file. It's a small seamingly meaningless change that was the difference with me being comfortable with TS vs. not -- screenshot here: http://imgur.com/CLTk3wB http://imgur.com/CLTk3wB
thewhitetulip 10y ago
Can anyone guide me about writing angularJS apps with Go backend? So far, I have not been able to find a good source to learn it.
- dfsegoat 10y ago
  FWIW as someone who struggled early on with the "How do i use angular with <other technology that i work with>?" question. It's important to IMMEDIATELY understand that the backend should not matter - so long as it returns JSON (or even XML i suppose) which AngularJS 1.x can consume with $http or $resource (or ng 2.x equivalent). This is an advantageous pattern in my opinion because the front-end angular application is totally decoupled from the backend (we have separate code repos - and even separate developers) - you can keep the backend as Go, or PHP, or Python - or even a static JSON file with something like jsonserver. So long as the JSON is formatted appropriately and API does what angular expects - angular does not care!
  - thewhitetulip 10y ago
    This is great advice! What do you think about routing? angular has it's own router, so can Go have. What to choose?
    - dfsegoat 10y ago
      I can only tell you what I know from experience: We use angular as an MVW for front-end We use django + django-rest-framework for back-end. It's important to understand that "routing" in angular is a bit "synthetic" - it's not actually requesting much from the server after index.html loads (it only changes address etc as part of the routing). So the routing is totally separate on the front-end, assuming you are using a back-end to provide the data.
    - DCoder 10y ago
      You don't choose between those two routers, they are not replacements for each other. At the risk of stating the obvious, the Angular router handles routing for the Angular frontend, the Go router handles routing for the Go backend (the initial page load, the AJAX calls made from Angular to get data...).
pramttl 10y ago
I have been using Angular 2 for 3 months now and so far have loved it (except for the breaking changes in RC series and updating each time). Glad 2.0.0 is here. Here are the few things I loved, amongst other interesting features: 1. Typescript awesomeness: You can write plain JS or give type hints in Typescript. Typescript is awesome, because it is a superset of Javascript and compiles to Javascript. (Typescript > ES6 > ES5) 2. Modular code: It is is much easier to manage Angular code as it grows (compared to AngularJS). Components could be made independently and reused within other components using component interaction [1] (@Input, @Output) 3. Template Directives: .html template directives are available unlike ReactJS. A ReactJS vs Angular2 blog post online [1] argued that that putting HTML in Javascript is better than putting Javascript in HTML. I'd argue that template directives like ngFor, ngIf, etc are much simpler to understand. Also, it is easier to collaborate with a designer/half-developer who knows some html/scss and doesn't know Javascript than working in ReactJS where every collaborator has to know JS. This way, it is also easier for someone to gradually learn the framework. For me, template directives are a big win. If someone wants to construct templates with plain JS, that is still possible in Angular. 4. @angular/router is better than AngularJS routing and we don't have to use a 3rd party library (like ui-router was more popular in AngularJS than the angularjs router) One thing that I have found annoying is that: UI libraries for Angular. Example: material2 (currently at alpha.8) [3] are not complete yet and lack several useful components. This can be a problem if you are looking to quickly build a complete, good looking UI. Hopefully, now with Angular 2.0.0 out; Angular team could focus on quicker development of material2, so we have all the AngularJS Material UI goodness with Angular. [1] https://angular.io/docs/ts/latest/cookbook/component-communication.html https://angular.io/docs/ts/latest/cookbook/component-communi... [2] https://medium.freecodecamp.com/angular-2-versus-react-there-will-be-blood-66595faafd51 https://medium.freecodecamp.com/angular-2-versus-react-there... [3] https://github.com/angular/material2 https://github.com/angular/material2
- dfsegoat 10y ago
  Awesome - thanks so much for this from a team running 1.3 in production (and looking now at moving to 2). Just curious if you are indeed saying that the built-in router allows you to do EVERYTHING you could do with ui-router (nested states / targeted views etc)? I was planning on sticking with ui-router-ng2 when we kick over to angular 2. How about testing? Was that difficult moving test suites over?
EugeneOZ 10y ago
I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You don't need any "bridges" anymore to use 3-rd party JS libraries inside your Angular app. Nothing need to be "angularized" - twbs, D3, all just works out of the box. Maybe it's even most important part for me. 3. Idea of `(events)` and `[attributes]` is awesome, works really effective and makes code much more easy to read. 4. Performance is great. 5. Community is friendly and have a lot of fun and patience, even to newbies. 6. TypeScript gives a lot of bonuses with zero price - you don't need to learn anything (you can just rename js to ts and it will work) and additions to JS are simple and powerful. 7. Cool abilities like AOT-compilation, server-side rendering and tree-shaking. Congrats to the all devs who are using Angular, congrats to the Angular team! :)
- dfsegoat 10y ago
  What about angular CLI - ? have you found that useful in your workflow?
  - pramttl 10y ago
    I have found Angular CLI productive, because it helps quickly generate components (each component has an html, ts, css, and spec.ts file with some boilerplate code). It is fairly quick to get up and running with angular-cli as compared to writing a webpack configuration file. However, since angular-cli is in beta, it lacks the flexibility that using webpack directly would offer. (P.S: Angular-CLI latest release would be using webpack internally)
    - ausjke 10y ago
      their tutorial is still based on systemjs instead of webpack, not sure which loader ng2 is preferring, I hope it's the latter.
  - 10y ago
sergiotapia 10y ago
Question for Angular devs: Why would I use Angular 2 and risk being left in the wind like Google did with Angular 1?
- EugeneOZ 10y ago
  It's still maintained and they have curator for AngularJS 1.x still.
- jbigelow76 10y ago
  Why would you use any open source codebase and risk being left in the wind by the maintainers of said codebase?
  - sergiotapia 10y ago
    Faith. Google has already broken that faith with 1.0, why do I renew the faith?
- elmigranto 10y ago
  Go for Backbone, has been supported for almost 6 years now.
petilon 10y ago
I evaluated React and Angular 2 several months ago and picked React. Some of the issues I found in Angular 2: The HTML template in Angular 2 is stored in a string. This has several disadvantages: 1. Editors can't do syntax coloring. 2. Editors can't do auto-indenting. 3. Editors can't offer "intellisense" suggestions. 4. Editors can't match tags. You embed variables in this template string like this: '<div>{{hero.name}}</div>'. This means: 1. Compilers can't find typos or find syntax errors at compile time. 2. If you make a typo in the variable name you don't get a compile-time or run-time error, instead the value is simply not displayed! 3. Tools can't refactor (i.e., rename) variables embedded inside the template. 4. No intellisense for the embedded expressions. You have to learn weird syntax such as ngFor whereas in React you just use a JavaScript for loop. In React you embed HTML inside the TypeScript and VisualStudio treats both the HTML and the TypeScript as first-class citizens. You get compile-time checks and intellisense for both the HTML and the TypeScript code! You can even put breakpoint inside the template and step through loops whereas in Angular you can't step through an ngFor. Note that some of the above may have changed since I last looked at Angular 2.
- beefsack 10y ago
  The template vs. JSX argument is highly subjective; a lot of people go the other way because language extensions break existing plugins, require extra build tooling, and add complexity.
  - DCoder 10y ago
    The same could be said about the "JavaScript vs TypeScript" argument. I can see that argument, but in my opinion, the safety nets provided by TypeScript and TSX are well worth the initial learning curve.
- dfsegoat 10y ago
  Which editors? JetBrains Webstorm has the same things for both Angular2 and React. https://www.jetbrains.com/webstorm/whatsnew/#v2016-2-angular-2 https://www.jetbrains.com/webstorm/whatsnew/#v2016-2-angular... I do agree that I really really was a fan of the backticks for ES6 / react for templating. Avoiding the whole " vs ' escaping nightmare is something i've always looked forward to. That seems like a very simple fix for them though, potentially. edit: tone
nsxwolf 10y ago
I'd be interested to hear people's experiences with running Angular 1 and 2 side by side in the same application for the purposes of incrementally migrating an Angular 1 codebase.
deleted 10y ago
[deleted]
partycoder 10y ago
Angular's module syntax, while it makes sense, it's just easiest way to get version control merge conflicts. Even easier than import statements... since these can be put into oneliners.
sturmeh 10y ago
Can't wait for Angular 3!
_alexander_ 10y ago
As see I on github there are lot of issues - https://github.com/angular/angular/milestone/58 https://github.com/angular/angular/milestone/58 for final release., however they released it. These issues are not important? Who can clarify?
huuu 10y ago
Is there a way to download Angular2 as Javascript file? Last time I checked I had to install loads of software just to start a Angular project.
- pramttl 10y ago
  You can still use the old way of using <script src=..>. See index.html in the following plunkr (sample angular app): http://embed.plnkr.co/xTyGA7Klq8Mta2T1yANh/ http://embed.plnkr.co/xTyGA7Klq8Mta2T1yANh/
jiggly_piff 10y ago
I dont understand why they claim you can make native mobile apps with angular2 ionic and native are two very different things
- robwormald 10y ago
  Because of projects like https://www.nativescript.org/nativescript-is-how-you-build-native-mobile-apps-with-angular https://www.nativescript.org/nativescript-is-how-you-build-n... We also have a (community) react-native bridge, and of course all the awesome html5 stuff from Ionic.
- jbigelow76 10y ago
  Nativescript [1] allow for fully native (no native webview wrapper) apps being built with Angular 2 on top of Nativescript. 1. https://www.nativescript.org/ https://www.nativescript.org/
  - DonHopkins 10y ago
    I'd love to hear the experiences and opinions of anyone who knows about building iOS and Android apps with NativeScript and Angular 2 [1], or who has used NativeScript [2] itself, please. NativeScript has a JavaScript<=>Java bridge on Android, and a JavaScript<=>Objective C bridge on iOS, like a cross platform version of Apple's ObjC bridge used in OS/X JavaScript for Automation [3] [4] [5] (but AFAIK Apple's ObjC bridge is apparently not available for developers to use as a framework, nor on iOS, nor of course on Android). Unlike React Native's JavaScript engine, it runs in the UI thread, using V8 on Android and JavaScriptCore on iOS, and you can call all the platform specific APIs directly, subclass and implement Java classes and Objective C classes and protocols, call methods and functions, and pass objects back and forth, write your own plugins in TypeScript, JavaScript, Java, Objective C, etc. [1] http://docs.nativescript.org/angular/tutorial/ng-chapter-0 http://docs.nativescript.org/angular/tutorial/ng-chapter-0 [2] https://www.nativescript.org/ https://www.nativescript.org/ [3] https://developer.apple.com/library/content/releasenotes/InterapplicationCommunication/RN-JavaScriptForAutomation/Articles/Introduction.html https://developer.apple.com/library/content/releasenotes/Int... [4] http://tylergaw.com/articles/building-osx-apps-with-js http://tylergaw.com/articles/building-osx-apps-with-js [5] http://developer.telerik.com/featured/javascript-os-x-automation-example/ http://developer.telerik.com/featured/javascript-os-x-automa...
julenx 10y ago
Announcement URL http://angularjs.blogspot.ch/2016/09/angular2-final.html http://angularjs.blogspot.ch/2016/09/angular2-final.html
mgadams3 10y ago
AngularClass's free project-based course on Angular 2 by Scott Moss has been pretty popular in the release candidate stage with 10k students so far. Will be getting updates with official release changes soon. http://courses.angularclass.com/p/angular-2-fundamentals http://courses.angularclass.com/p/angular-2-fundamentals
awjr 10y ago
Looking at https://github.com/angular/angular/milestones https://github.com/angular/angular/milestones I was slightly surprised to see 30 outstanding issues. Reading the announcement they have been careful to bring semver into the mix. This should speed up release as well as start bringing through some of the 2.1 stuff quicker.
boxctim 10y ago
"Loved by Millions" might be overstating things a bit
- arc_of_descent 10y ago
  Classic sales talk, huh? Devs must be in the thousands, but the users of their apps might figure in the millions :)
  - h1d 10y ago
    Users don't necessarily love the underlying framework being used though.
    - softawre 10y ago
      This just in: billions love javascript!
doczoidberg 10y ago
Nodody mentioned angular universal here. I think it's a big win to prerender the SPA on the server. It's faster, more mobile friendly and pages can be indexed by search engines. IDEs have to implement better support for NG2 but this will come over time.
- j_jochem 10y ago
  As far as I know, Google does index SPAs that are only rendered in the browser.
  - doczoidberg 10y ago
    Google does not index my ng2 site without prerendering. There will be always limits for search engines on interpreting js.
    - j_jochem 10y ago
      That's interesting. I previously researched this with regard to React apps, and the tenor was that server-side rendering was no longer required in order to get indexed by Google. Google itself has this to say: https://webmasters.googleblog.com/2014/05/understanding-web-pages-better.html https://webmasters.googleblog.com/2014/05/understanding-web-... Have you tried to figure out the cause using Search Console?
      - Bahamut 10y ago
        I have also encountered an Angular 1 app in the wild that was indexed by Google, but there are limits to the ability of their crawler - it apparently didn't follow through to other pages.
waltero 10y ago
Nice, played around with Angular 1 and 2 - Angular2 with its use of components reminded me of making front-ends with the Apache Wicket framework some time ago. This might appeal to java full stack/backend engineers that need to once in while show case a nice and shiny GUI. It my experience, the combo of Angular with Bootstrap/Font awesome works just fine for that. Very positive to have static typing through TypeScript as well. But also here I am quite biased for I never liked the concept that 'everything is just a var' ;)
ergo14 10y ago
It is interesting how people are debating here, angular this, react that... Yet there is Polymer that just works, has a great ecosystem, awesome material design support and is a breeze to work with (+ its fast too). Right now there was 2.0 announcement and new version really supports easy migration path unlike Angular 2.x.
- prohor 10y ago
  Polymer and Angular 2.0 seems to have a lot concepts in common and I don't fully understand why they are going to compete, given they come from the same source. But for me it seems that Polymer nowhere picked up as Angular. When it comes to performance it is great in Chrome. In other browsers not so. I hope v2 will be much better once they can get rid of the compatibility layer for other ever-green browsers.
  - ergo14 10y ago
    Have you actually benchmarked polymer in a non-chrome browser? It is much faster than Angular - somewhere around React performance. Polymer is picked up by big companies already whereas "no one"(big) is using angular 2.x for now. People here seem to project a weird bubble around Angular/React. > In other browsers not so. I hope v2 will be much better once they can get rid of the compatibility layer for other ever-green browsers. Browsers get rid of it on their own - when they implement the standards, shims load when specific functionality is found or not.
    - prohor 10y ago
      I'm not comparing against Angular (which in v1 is known not to be super fast) just between browsers. I was mainly looking at https://vaadin.github.io/gwt-polymer-elements/demo/#gwt/JavaApiWidget https://vaadin.github.io/gwt-polymer-elements/demo/#gwt/Java... . It uses a lot of widgets on one page. Take a look how on loads in Chrome, Firefox, Edge (refresh to minimize network effects). I didn't go really deep in it, but first look was that lots of time was used in registering custom elements. Sure, here it is wrapped in GWT (which would be my case), but it doesn't seem to add much, rather the fact it loads all widgets from Polymer.
kabes 10y ago
Look at the weekly meeting notes: http://g.co/ng/weekly-notes http://g.co/ng/weekly-notes . So 3 days ago they were talking about an rc7 to test out and now all of the sudden we've got a final?
nagarjun 10y ago
How does the Angular CLI compare to the Ember CLI? Also, how does Angular 2 compare to Ember 2.8?
- szines 10y ago
  Angular CLI is actually Ember CLI under the hood. You cannot really compare these frameworks because Ember is far ahead of all. Super stable, matured, adopted the best practices, huge addon ecosystem, brilliant community, easy to learn, great documentation. Quite an obvious abd best choice. Life and development is just super easy and fast with Ember.
kensign 10y ago
Before you consider Angular 2, do yourself a favor and check out http://aurelia.io http://aurelia.io. Compare the differences and consider the trade offs with complexity vs simplicity. It's worth a consideration.
- stephenhuey 10y ago
  Please! The more of you that join us in Aurelia the better it will be, and I think the Angular community will benefit as well because at least they would become aware of some more best practices they could use to improve Angular.
rukenshia 10y ago
So I have never used Angular before but work with Vue. Looking at the tutorial, why is there the syntax of [(ngModel)] (equivalent would be v-model for me) and ngFor= (v-for)? Why are they different? It looks kind of unnecessary to me. I would really appreciate if someone explained it.
- zygimantasdev 10y ago
  [()] indicates two-way binding. If you curious you can read more in docs [1], while ngFor is just an attribute directive which changes DOM [2] [1] - https://angular.io/docs/ts/latest/guide/template-syntax.html#!#two-way-binding-with-ngmodel https://angular.io/docs/ts/latest/guide/template-syntax.html... [2] - https://angular.io/docs/ts/latest/guide/attribute-directives.html https://angular.io/docs/ts/latest/guide/attribute-directives...
KyoChunho 10y ago
It's a fantastic framework and I'm looking forward to building a ton of cool stuff with it. Though next week's announcement... Angular 2.0.1 RC 1 It's Change Log will read: * Routing has been rebuilt.. all previous versions not compatible * We decided to rename the NgModule decorator to NgYouMAD? * All Internet tutorials no longer work... Good Luck relearning!
WA 10y ago
Right now, I'm considering which works best for me. Requirements: App for Android & iPhone plus Web-based app. The most complex part is a Graph with interactions (such as highlighting a specific value). It should feel snappy, although I don't make heavy use of neither gestures nor OS-related features. Ionic 2 + Angular 2 seem to be the best choice, since I can basically write the app once and release for all three platforms. React Native has the downside that React and React Native are two different things. Be aware that there is no such thing as React Native for the web. There's something in development right now, but nothing stable. Truly native: I can't support three platforms as a single developer and I don't feel like outsourcing it. I'll go with Ionic 2 + Angular 2, although Ionic 2 still has quite a few bugs. For example, the zoom attribute on <ion-scroll> doesn't work – which is critical for my app. Sure, there are hacks and this reminds me on the discussion from the other day: https://news.ycombinator.com/item?id=12477190 https://news.ycombinator.com/item?id=12477190 Yes, it's all very hacky. But there's really no alternative I guess.
- rubber_duck 10y ago
  Check out nativescript, it's TS/angular 2 equivalent to React Native.
DigitalSea 10y ago
Rob Eisenberg and his nimble team beat Angular 2 to the punch all the way back in July when Aurelia final was released. Before considering Angular, considering checking out http://aurelia.io http://aurelia.io - easier to learn, no third party dependencies and great support. I applaud the Angular team for sticking it out, but I am afraid they released far too late to compete with the likes of React, Vue and so on.
- rpeden 10y ago
  You might be underestimating how much inertia the Angular name has in larger enterprise dev shops. They're still creating new projects in Angular 1.x, and will eventually starting using Angular 2 just because it is called Angular.
- oneshoe 10y ago
  I now have several Aurelia apps in production. I've also created an app in Angular (v1), and another using Ionic (v1) - which was great. But, I can't express how well Rob and his team executed on this project. Documentation could be a little better in a couple areas but this is a place where they've done extremely well also (contradiction I know - but, for example the cheat sheets are amazing and documentation is complete on most things but there are some classes that are still not documented well enough). If you want to develop in Aurelia - just the community on Gitter - they are extremely responsive and very helpful.
  - stephenhuey 10y ago
    The documentation has been improving since January, and I expect there to be plenty more in a short time because for over half a year they were focused more on getting from beta to a full release. But even with the cheat sheets it felt like there was plenty to get work done because the complexity isn't so high with Aurelia - less to get confused about! And I agree about the Gitter channel being very friendly.
deleted 10y ago
[deleted]
SonicSoul 10y ago
congrats to ng-team! funny i just spent an hour yesterday upgrading to 3.0.0-rc.7 I see their quick start has been updated to use the final. https://angular.io/docs/ts/latest/quickstart.html https://angular.io/docs/ts/latest/quickstart.html <= great way to get started. agree with other comments that RxJS is a tough library to learn but I love that they used it instead of re-inventing that wheel. It is incredibly powerful and solves a lot of asynchronous programming problems. you can see all of the methods visualized with marbles here: http://rxmarbles.com/ http://rxmarbles.com/
- jffry 10y ago
  Surely you know that 3.0.0-rc.7 was deprecated in favor of 3.0.0-rc386, right? :-p
gravypod 10y ago
I like that they are selling the fact they have good ide support.
dschiptsov 10y ago
How many hundreds of npm dependencies in the default install? Is Leftpad included?
- renke1 10y ago
  Why does it matter?
  - rajangdavis 10y ago
    http://www.haneycodes.net/npm-left-pad-have-we-forgotten-how-to-program/ http://www.haneycodes.net/npm-left-pad-have-we-forgotten-how... TL;DR: Left Pad is a NPM package that was removed by it's author in protest. Apparently, a ton of other packages broke as it was a major dependency across the NPM ecosystem.
scotchio 10y ago
Shameless plug: Free Getting Started Video Course on Scotch.io Getting Started with Angular 2 https://school.scotch.io/getting-started-with-angular-2 https://school.scotch.io/getting-started-with-angular-2
martyn80 10y ago
The angular website itself still uses 1.4.8? I can't find a benchmark or size comparision somewhere.
deleted 10y ago
[deleted]
electrotype 10y ago
Serious question : Why are SPA frameworks so popular these days? When someone asks "What should I use for web development?", It's now all about React/Angular/Ember/etc. But when I look at how are built the sites I like and visit frequently, I'd say 95% of them are not SPA, they are classic sites where the server generate each page (sometimes with one or two Ajax requests)! The Single Page pattern is great for desktop-like applications such as Gmail, it's obvious. But otherwise, I don't know... I think I still prefere the "feel" of classic websites.
- overcast 10y ago
  Prevalence of API's. One common interface to query/update from. You don't have to do both server side, and client side requests. Rather do it all client side. I've done of a few of these types, and now have moved onto mixed environments. Where most is rendered server sided, then only updates requested client side. Of course you're doing things twice for same queries.
- scottmmjackson 10y ago
  SPA frameworks are not all-encompassing tools for buildong all web pages. Notably, trying to SEO a SPA is frustrating at best and impossible at worst. However, in b2b use cases where SEO isn't an issue, SPA frameworks are ideal for coordinating a static-site<->dynamic-api system.
  - pault 10y ago
    Server-side rendering is supported in several SPA frameworks now, and SEO is not an issue if you use it.
  - quaunaut 10y ago
    Google's been indexing SPAs fine for quite awhile.
  - charrondev 10y ago
    React, Angular 2, Vue 2 and some other SPA frameworks or view systems all support server-side rendering with very little coercion nowadays. That combined with google executing javascript during indexing means that SEO isn't nearly the issue it used to be.
jcadam 10y ago
Never used Angular. I was considering it for one project, but the uncertainty around the whole Angular 1/2 thing made it too risky, so I stuck with what I knew at the time (Backbone/Marionette). Tried Ember.js more recently, didn't much care for it. I think I'm just not a fan of large frameworks. Now mithril.js (http://mithril.js.org/ http://mithril.js.org/) has finally lured me away from Backbone :)
cubef 10y ago
I've been developing a large web app with ng2 and Dart since april, no framework is perfect, but this combo is a joy to work with. Did ng1 and react with JS before, react was more enjoyable but in the end it just doesn't compare. Anyway, great to see the release :)
leshow 10y ago
the website is barely functional for me, the anchor links in the documentation don't even work.
BigJeffeRonaldo 10y ago
Who cares
- sctb 10y ago
  Please comment civilly and substantively on HN or not at all. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
kingofhawks 10y ago
Congratulations!
nbevans 10y ago
At first I read this article title as "Angular 2 Finally Released" :)
deleted 10y ago
[deleted]
georgefrick 10y ago
As a developer who didn't care for Angular 1.x and strongly argued in favor of a simple approach for years (Backbone, etc). I've been using Angular 2 in a major enterprise project since RC1. Even with some of the headaches between RC releases; all of the reasoning behind those changes is technically sound. It's easy to write components and wire everything, and even small things like async validators are fluid and easy to implement. I'm loving it, and while the entire build system is still a bit of a dumpster fire; we're doing great on things like testing, code coverage; etc. There are a lot of problems with lazy developers hoping a blog will tell them how to do every little thing. The source code is on Github. If you can't get something working right; maybe go read the source code of the classes you are interacting with. I've found 99% of the time now that simply reading through the code gives me not only the transparency needed, but a clear path to a better solution. Kudos to them on the new forms; they're awesome.
- Bahamut 10y ago
  One thing that is hugely helpful that many developers don't do is read the tests for the library they use - in particular with Angular, reading the tests in the Angular codebase actually assist greatly in how to use a feature.
deleted 10y ago
[deleted]
omouse 10y ago
I heard that a particular company, Rangle, worked on AngularJS2 and from what I've heard of them they're an MVP/dev-agency so it isn't surprising to see some of the complaints here about broken backwards compatibility and bad documentation around testing. Seems few people know how to steward a free/open source software project that has lasted over 5 yrs.
- Bahamut 10y ago
  Rangle only created an Angular 2 successor to Batarang. They had nothing to do with core Angular 2 development. Angular 2 in beta/rc was in many ways rapid iteration on top of experimentation to get the core APIs & developer experience right. They have finally reached a stability point where they feel completely comfortable with the framework they have ended up with as a result, thus the formal release of 2.0. If you've actually paid attention to the development cycle of Angular 2, it was very fast - it turns out that Google moves much faster than most shops, which was seen in full display during alpha/beta/rc. However, that goes with the territory there, and the versioning did not lie. It is now following semver though, so we shouldn't be hearing of these problems anymore.
morsmodr 10y ago
frameworkFatigue++
alabamamike 10y ago
Thanks and congrats to the Angular2 team! We've been building on the release candidates since March, and we're happy to see the breaking changes come to an end.
chillypenguin 10y ago
I wonder what "Final" even means in this context. Google has already admitted that the Angular team uses the term "Release Candidate" to mean something completely different to how every other software company in the universe understands it. (Listen to Adventures in Angular podcast, episode 105.) A very rocky road ahead, methinks.
rochak 10y ago
Was waiting for its final release. Recently built an app using it and the documentation kept changing. Found it hard to keep up.

838 points by mikeryan52 10y ago

Front end development is crazy these days. I remember on my road to learning Java EE banging my head on the wall trying to put together things like dependency management with Maven, ORM's, and all sorts of arcane concepts and patterns. It took me a long time to get to that point but now it seems all too familiar. As someone coming up to speed with frameworks like React and Angular 2 it feels like that all over again.

crypto5 10y ago
I think in angular everything is already tied together, and you just write code.
jacobsenscott 10y ago
That's Conway's law for you. All three frameworks were built by meglogcorp, and they all feel exactly the same. It is funny that after the Rails driven success web devs had moving away from J2EE they are falling right back into the same traps - ultra complex bloated frameworks built on a terrible language.
- arahaya 10y ago
  Symfony comes to mind. It's like a php clone of Spring.
- indexerror 10y ago
  > ultra complex bloated frameworks built on a terrible language Even if you consider JS a bad language, proper abstractions can change the face of it entirely. By your logic, assembly is also bad since it is absurd to write anything useful in it. IMO Elm is a step in the right direction.
  - axihack 10y ago
    I've been doing a lot of FE for many years now and have worked with all major frameworks and I love JS and its flexibility. That being said I think we've been building one framework after another trying to abstract the things that make JS a language not suitable for state dependent apps. Elm feels like the right step compared to anything else out there.
- choward 10y ago
  Javascript is definitely a terrible language, but it is the only language for the web unless you consider languages that transpile to javascript. Are you suggesting not using a javascript framework, using a transpiled language instead of javascript, not writing any front end code at all, or doing something ridiculous like turbolinks?
  - bezzi 10y ago
    What is wrong with turbo links???
  - calsy 10y ago
    Why would you consider JS to be a terrible language? It's not a requirement to use a framework to code in JS.
    - jomamaxx 10y ago
      "Why would you consider JS to be a terrible language? " JS is kind of a 'bad language' because: 1) It's missing some pretty important things. Try to determine if a value is a number. Seriously. Look into that mess. Or anything else. Doing simple type-checking is crazy, and we basically are resigned to 'best practices' - which is crazy. 2) Prototype chaining is a neat idea and has some merits - but in reality it makes things super-duper complicated. Ask 10 JS devs how it works and get 21 answers. That is bad. 3) Almost nothing is built in. You need to use a lot of 3rd party libs to do common things. 4) There is no such thing as 'JS' - ever browser, every version - you get completely different implementations. Maybe we can't blame 'JS' - but pragmatically, this means JS is a problem. A minor issue is issues with packaging, encapsulation and scale, which is also a function of loose typing. When JS programs get complex, they get unruly, and you wish you might be able to do things in an OO language at that point. JS is really light, and that has advantages - and I think it's the best language for a lot of async things - and UI's are inherently async - so that's good. In 5-8 years JS might be 'stabilized' in terms of libs or de-facto standards and it will grow. To anyone who's programmed in other, more established languages, I think it's clear JS has some weirdness that doesn't need to be there. But I like it.
freyr 10y ago
That's funny; as someone familiar with React, Angular, etc., the Java ecosystem seems utterly impenetrable.
- dfsegoat 10y ago
  Yeah - we consult with an angular + Java group (for angular only) --- I can't understand half of what they are talking about when they talk about Enterprise level Java web projects. Java for Hadoop, Spark etc I work with daily.
  - eitally 10y ago
    Enterprise projects tend to have way more convoluted business logic and interfaces than consumer stuff -- it doesn't get nearly the love it deserves imho. Those developers, DBAs, devops folks, and sysadmins suffer sooooo much every day.
    - waltero 10y ago
      absolutely - but typically you can't get all this pain across to the 'business' because of an enormous lack of understanding. As long as the buttons in the GUI look nice and shiny, who cares what happens further under the hood..
    - j_jochem 10y ago
      Java EE is basically an excuse for consultants to overcharge for overengineering solutions to problems that were already complex to begin with. Source: Did some Java EE consulting here and there.
  - deleted 10y ago
    [deleted]
eternalban 10y ago
I venture a guess that you learned JEE by rote and not from first principles. Learning by rote is stressful since your mind has to retain effectively a bag of (to it incomprehensible) technical trivia. In contrast, first principles are compact and generative, and such a grasp also informs your intuition so you can actually make educated guesses and jump in the deep end when picking up a new stack. Same principles apply to learning programming languages. The biggest headache in picking new stacks today is the current trend of technical neologisms, so a bit of initial squinting (for recognition) is required.
szines 10y ago
If you use Ember.js, which is the most matured and serious on the market, you never had that feeling that JS changes a lot. Consistent and continuous improvement. The best choice.
dlandis 10y ago
That's very true -- it is reminiscent of the old J2EE days 12+ years ago. But it didn't really take long back then for a consensus to emerge about how awful most of that technology was (enterprise java beans, etc) and for people to settle on more simplified, streamlined approaches. How long will it take for the momentum in the front end community to similarly shift away from these bloatware approaches?
- iamcreasy 10y ago
  I am a java programmer and I want to head towards web development. My first thought was learning JSP, Servlet and then move towards different frameworks like Spring. I don't know much - but can you tell me why JavaEE is an awful technology?

joshschreuder 10y ago

There's more info on future plans here: https://angularjs.blogspot.com.au/2016/09/angular2-final.html https://angularjs.blogspot.com.au/2016/09/angular2-final.htm... Specifically: > Bug fixes and non-breaking features for APIs marked as stable > More guides and live examples specific to your use cases > More work on animations > Angular Material 2 > Moving WebWorkers out of experimental > More features and more languages for Angular Universal > Even more speed and payload size improvements And immediately: > Semantic Versioning

Lx1oG-AWb6h_ZG0 10y ago
Ha! I foolishly thought that when ng2 hit RC, it actually meant things would be stable. Keeping up with the ridiculous amount of breaking changes (the router, for example) through the RC versions was a horrible experience.
- xeromal 10y ago
  Hahaha. No shit. Stackoverflow would be like "You are using the wrong router. Use version x." Then someone said "No, version x is deprecated as of last night. Use version z. They skipped y after abandoning that too."

chrisballinger 10y ago

I expected angular.io to be a flashy example Angular 2 SPA and was disappointed when I realized it was just a regular old static HTML website. I guess most of the content is more suited for a static site. At least the search bar on the docs page looks like it has some Angular going on. Also it would be neat if the docs had dynamic examples instead of screenshots.

borplk 10y ago
Same. I think it would be a nice statement to make if angular.io itself was an Angular app that was a joy to use.
unknowingone 10y ago
But can it compete with this? https://react-bootstrap.github.io/components.html https://react-bootstrap.github.io/components.html
- Bahamut 10y ago
  I think ultimately ng-bootstrap* (https://ng-bootstrap.github.io/ https://ng-bootstrap.github.io/) will be better, but I'm biased. API signature looks much better than shoehorning everything into components that don't belong there - we have a lot of work to go though, so it currently is still a work in progress. * I am a part of the UI Bootstrap/ng-bootstrap team - we worked on ng-bootstrap starting back in last August/September and have the benefit of two of our team members currently working on the Angular team.
  - winstonewert 10y ago
    Could you elaborate on what you mean by "shoehorning everything into components that don't belong there"?
    - Bahamut 10y ago
      There seems to be a lot of advocacy for tossing everything into the component tree in the React ecosystem - recently I got linked to a snide remark by Ryan Florence on Twitter implicitly arguing for putting everything in the component tree, including constructs that should have a better separation such as routing (which the tweet appeared to be a reference to). Some services don't belong in JSX though - this is why you have the idea of stores in Flux/Redux/etc. Some data doesn't make sense to couple to the component hierarchy - doing so makes it very easy to create dependencies on the component tree, which decreases modularity, as well as has perf ramifications by increasing the DOM elements that get rendered unnecessarily by React. Some examples are data models, routing, and interactions with non-element DOM api (window.location, XHR, etc.). This also has a side-effect of increasing difficulty of testing what generally should be vanilla constructs not tied to various frameworks/libraries unnecessarily.

stevehiehn 10y ago

Yes!!, I was starting to get nervous I jumped the gun using it at work!

gkoberger 10y ago

As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.

deleted 10y ago
[deleted]
Pfhreak 10y ago
As someone who uses React currently, this would be useful to me too.
irrational 10y ago
Or Vue.js, or Inferno, or...
asher_ 10y ago
I'm currently in the same boat. Both are similar in that they are component-oriented. There are two important factors in my mind. 1. The ecosystem (as you mentioned). React has a clear head start here, but I expect Angular2 to make some gains over time. 2. Angular2 gives you a full framework, and as they say now, a whole platform. React is smaller and you rely on a bunch of other packages to get all the extra features you need. If you want a full solution, Angular2 gives you that. This can be argued as a good thing or a bad thing. More flexibility with React, but also more things you need to figure out and make a decision about. With Angular2, once you buy in, you don't need to make all of those decisions. In my particular circumstance, which is to migrate an Angular1 app to a newer framework over time (mainly for the server side rendering features), Angular2 provides a clearer path and offers some nifty features like component styles that allow a similar migration with CSS.
- BigJono 10y ago
  As someone who has never used Angular but is interested in Angular 2, can you give some examples of the framework-y things it provides that React doesn't? Redux is really the only thing I find necessary for what I've developed so far, and I'm sure Angular has it's equivalent, but what else does it have?

mshenfield 10y ago

Found this pretty helpful in grasping differences between angular 1 and 2. https://angular.io/docs/ts/latest/cookbook/a1-a2-quick-reference.html https://angular.io/docs/ts/latest/cookbook/a1-a2-quick-refer...

wcarss 10y ago

Is there a definitive angular versus react versus ember (or others) pros/cons/community status page out there somewhere?

dfsegoat 10y ago
Remember though, Angular is an (opinionated) framework, react is a lightweight library.
- Nemcue 10y ago
  I wish people would just stop pointing this out. While technically true when people refer to React they're referring to the canonical stack that people use (i.e. + Redux).
  - ng12 10y ago
    I don't think that makes a difference. I can take a scalpel to my Redux code without really worrying about how it affects my React code. This is why I use React + Redux with some Webpack magic -- everything is encapsulated and composable from the ground up.
Grangar 10y ago
Not definitive, but there are a lot of good comparisons: http://smashingboxes.com/blog/choosing-a-front-end-framework-angular-ember-react http://smashingboxes.com/blog/choosing-a-front-end-framework... https://www.developereconomics.com/feature-comparison-of-4-popular-js-mv-frameworks https://www.developereconomics.com/feature-comparison-of-4-p... https://www.developereconomics.com/comparison-4-popular-javascript-mv-frameworks-part-2 https://www.developereconomics.com/comparison-4-popular-java...
swalsh 10y ago
You know what, these religious debates need a war to settle the question. Let's get 3 of the best teams for each stack, have them build the same 4 apps that cover a few of the most common scenarios... and let's see who's solution is done the fastest, is most maintainable, and has the best performance.

meltbuzz 10y ago

nice

xuwupeng2000 10y ago

I am on the boat of Angular 1. I really want to move to React cuz I don't want to learn TypecScript.

eyelidlessness 10y ago
FWIW you already know TypeScript, it's a superset of JavaScript (though you'll get few benefits from that).
alxhub 10y ago
Even if you use React, you should try Typescript. Totally worth it.
- morsmodr 10y ago
  +1 Billion minimum for this comment
dfsegoat 10y ago
I was really frightened with it. But webstorm from jetbrains has an EAP version which basically shows your compiled JS file "nested" under your typescript file. It's a small seamingly meaningless change that was the difference with me being comfortable with TS vs. not -- screenshot here: http://imgur.com/CLTk3wB http://imgur.com/CLTk3wB

thewhitetulip 10y ago

Can anyone guide me about writing angularJS apps with Go backend? So far, I have not been able to find a good source to learn it.

dfsegoat 10y ago
FWIW as someone who struggled early on with the "How do i use angular with <other technology that i work with>?" question. It's important to IMMEDIATELY understand that the backend should not matter - so long as it returns JSON (or even XML i suppose) which AngularJS 1.x can consume with $http or $resource (or ng 2.x equivalent). This is an advantageous pattern in my opinion because the front-end angular application is totally decoupled from the backend (we have separate code repos - and even separate developers) - you can keep the backend as Go, or PHP, or Python - or even a static JSON file with something like jsonserver. So long as the JSON is formatted appropriately and API does what angular expects - angular does not care!
- thewhitetulip 10y ago
  This is great advice! What do you think about routing? angular has it's own router, so can Go have. What to choose?
  - dfsegoat 10y ago
    I can only tell you what I know from experience: We use angular as an MVW for front-end We use django + django-rest-framework for back-end. It's important to understand that "routing" in angular is a bit "synthetic" - it's not actually requesting much from the server after index.html loads (it only changes address etc as part of the routing). So the routing is totally separate on the front-end, assuming you are using a back-end to provide the data.
  - DCoder 10y ago
    You don't choose between those two routers, they are not replacements for each other. At the risk of stating the obvious, the Angular router handles routing for the Angular frontend, the Go router handles routing for the Go backend (the initial page load, the AJAX calls made from Angular to get data...).

pramttl 10y ago

I have been using Angular 2 for 3 months now and so far have loved it (except for the breaking changes in RC series and updating each time). Glad 2.0.0 is here. Here are the few things I loved, amongst other interesting features: 1. Typescript awesomeness: You can write plain JS or give type hints in Typescript. Typescript is awesome, because it is a superset of Javascript and compiles to Javascript. (Typescript > ES6 > ES5) 2. Modular code: It is is much easier to manage Angular code as it grows (compared to AngularJS). Components could be made independently and reused within other components using component interaction [1] (@Input, @Output) 3. Template Directives: .html template directives are available unlike ReactJS. A ReactJS vs Angular2 blog post online [1] argued that that putting HTML in Javascript is better than putting Javascript in HTML. I'd argue that template directives like ngFor, ngIf, etc are much simpler to understand. Also, it is easier to collaborate with a designer/half-developer who knows some html/scss and doesn't know Javascript than working in ReactJS where every collaborator has to know JS. This way, it is also easier for someone to gradually learn the framework. For me, template directives are a big win. If someone wants to construct templates with plain JS, that is still possible in Angular. 4. @angular/router is better than AngularJS routing and we don't have to use a 3rd party library (like ui-router was more popular in AngularJS than the angularjs router) One thing that I have found annoying is that: UI libraries for Angular. Example: material2 (currently at alpha.8) [3] are not complete yet and lack several useful components. This can be a problem if you are looking to quickly build a complete, good looking UI. Hopefully, now with Angular 2.0.0 out; Angular team could focus on quicker development of material2, so we have all the AngularJS Material UI goodness with Angular. [1] https://angular.io/docs/ts/latest/cookbook/component-communication.html https://angular.io/docs/ts/latest/cookbook/component-communi... [2] https://medium.freecodecamp.com/angular-2-versus-react-there-will-be-blood-66595faafd51 https://medium.freecodecamp.com/angular-2-versus-react-there... [3] https://github.com/angular/material2 https://github.com/angular/material2

dfsegoat 10y ago
Awesome - thanks so much for this from a team running 1.3 in production (and looking now at moving to 2). Just curious if you are indeed saying that the built-in router allows you to do EVERYTHING you could do with ui-router (nested states / targeted views etc)? I was planning on sticking with ui-router-ng2 when we kick over to angular 2. How about testing? Was that difficult moving test suites over?

EugeneOZ 10y ago

I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You don't need any "bridges" anymore to use 3-rd party JS libraries inside your Angular app. Nothing need to be "angularized" - twbs, D3, all just works out of the box. Maybe it's even most important part for me. 3. Idea of `(events)` and `[attributes]` is awesome, works really effective and makes code much more easy to read. 4. Performance is great. 5. Community is friendly and have a lot of fun and patience, even to newbies. 6. TypeScript gives a lot of bonuses with zero price - you don't need to learn anything (you can just rename js to ts and it will work) and additions to JS are simple and powerful. 7. Cool abilities like AOT-compilation, server-side rendering and tree-shaking. Congrats to the all devs who are using Angular, congrats to the Angular team! :)

dfsegoat 10y ago
What about angular CLI - ? have you found that useful in your workflow?
- pramttl 10y ago
  I have found Angular CLI productive, because it helps quickly generate components (each component has an html, ts, css, and spec.ts file with some boilerplate code). It is fairly quick to get up and running with angular-cli as compared to writing a webpack configuration file. However, since angular-cli is in beta, it lacks the flexibility that using webpack directly would offer. (P.S: Angular-CLI latest release would be using webpack internally)
  - ausjke 10y ago
    their tutorial is still based on systemjs instead of webpack, not sure which loader ng2 is preferring, I hope it's the latter.
- 10y ago

sergiotapia 10y ago

Question for Angular devs: Why would I use Angular 2 and risk being left in the wind like Google did with Angular 1?

EugeneOZ 10y ago
It's still maintained and they have curator for AngularJS 1.x still.
jbigelow76 10y ago
Why would you use any open source codebase and risk being left in the wind by the maintainers of said codebase?
- sergiotapia 10y ago
  Faith. Google has already broken that faith with 1.0, why do I renew the faith?
elmigranto 10y ago
Go for Backbone, has been supported for almost 6 years now.

petilon 10y ago

I evaluated React and Angular 2 several months ago and picked React. Some of the issues I found in Angular 2: The HTML template in Angular 2 is stored in a string. This has several disadvantages: 1. Editors can't do syntax coloring. 2. Editors can't do auto-indenting. 3. Editors can't offer "intellisense" suggestions. 4. Editors can't match tags. You embed variables in this template string like this: '<div>{{hero.name}}</div>'. This means: 1. Compilers can't find typos or find syntax errors at compile time. 2. If you make a typo in the variable name you don't get a compile-time or run-time error, instead the value is simply not displayed! 3. Tools can't refactor (i.e., rename) variables embedded inside the template. 4. No intellisense for the embedded expressions. You have to learn weird syntax such as ngFor whereas in React you just use a JavaScript for loop. In React you embed HTML inside the TypeScript and VisualStudio treats both the HTML and the TypeScript as first-class citizens. You get compile-time checks and intellisense for both the HTML and the TypeScript code! You can even put breakpoint inside the template and step through loops whereas in Angular you can't step through an ngFor. Note that some of the above may have changed since I last looked at Angular 2.

beefsack 10y ago
The template vs. JSX argument is highly subjective; a lot of people go the other way because language extensions break existing plugins, require extra build tooling, and add complexity.
- DCoder 10y ago
  The same could be said about the "JavaScript vs TypeScript" argument. I can see that argument, but in my opinion, the safety nets provided by TypeScript and TSX are well worth the initial learning curve.
dfsegoat 10y ago
Which editors? JetBrains Webstorm has the same things for both Angular2 and React. https://www.jetbrains.com/webstorm/whatsnew/#v2016-2-angular-2 https://www.jetbrains.com/webstorm/whatsnew/#v2016-2-angular... I do agree that I really really was a fan of the backticks for ES6 / react for templating. Avoiding the whole " vs ' escaping nightmare is something i've always looked forward to. That seems like a very simple fix for them though, potentially. edit: tone

nsxwolf 10y ago

I'd be interested to hear people's experiences with running Angular 1 and 2 side by side in the same application for the purposes of incrementally migrating an Angular 1 codebase.

deleted 10y ago

[deleted]

partycoder 10y ago

Angular's module syntax, while it makes sense, it's just easiest way to get version control merge conflicts. Even easier than import statements... since these can be put into oneliners.

sturmeh 10y ago

Can't wait for Angular 3!

_alexander_ 10y ago

As see I on github there are lot of issues - https://github.com/angular/angular/milestone/58 https://github.com/angular/angular/milestone/58 for final release., however they released it. These issues are not important? Who can clarify?

huuu 10y ago

Is there a way to download Angular2 as Javascript file? Last time I checked I had to install loads of software just to start a Angular project.

pramttl 10y ago
You can still use the old way of using <script src=..>. See index.html in the following plunkr (sample angular app): http://embed.plnkr.co/xTyGA7Klq8Mta2T1yANh/ http://embed.plnkr.co/xTyGA7Klq8Mta2T1yANh/

jiggly_piff 10y ago

I dont understand why they claim you can make native mobile apps with angular2 ionic and native are two very different things

robwormald 10y ago
Because of projects like https://www.nativescript.org/nativescript-is-how-you-build-native-mobile-apps-with-angular https://www.nativescript.org/nativescript-is-how-you-build-n... We also have a (community) react-native bridge, and of course all the awesome html5 stuff from Ionic.
jbigelow76 10y ago
Nativescript [1] allow for fully native (no native webview wrapper) apps being built with Angular 2 on top of Nativescript. 1. https://www.nativescript.org/ https://www.nativescript.org/
- DonHopkins 10y ago
  I'd love to hear the experiences and opinions of anyone who knows about building iOS and Android apps with NativeScript and Angular 2 [1], or who has used NativeScript [2] itself, please. NativeScript has a JavaScript<=>Java bridge on Android, and a JavaScript<=>Objective C bridge on iOS, like a cross platform version of Apple's ObjC bridge used in OS/X JavaScript for Automation [3] [4] [5] (but AFAIK Apple's ObjC bridge is apparently not available for developers to use as a framework, nor on iOS, nor of course on Android). Unlike React Native's JavaScript engine, it runs in the UI thread, using V8 on Android and JavaScriptCore on iOS, and you can call all the platform specific APIs directly, subclass and implement Java classes and Objective C classes and protocols, call methods and functions, and pass objects back and forth, write your own plugins in TypeScript, JavaScript, Java, Objective C, etc. [1] http://docs.nativescript.org/angular/tutorial/ng-chapter-0 http://docs.nativescript.org/angular/tutorial/ng-chapter-0 [2] https://www.nativescript.org/ https://www.nativescript.org/ [3] https://developer.apple.com/library/content/releasenotes/InterapplicationCommunication/RN-JavaScriptForAutomation/Articles/Introduction.html https://developer.apple.com/library/content/releasenotes/Int... [4] http://tylergaw.com/articles/building-osx-apps-with-js http://tylergaw.com/articles/building-osx-apps-with-js [5] http://developer.telerik.com/featured/javascript-os-x-automation-example/ http://developer.telerik.com/featured/javascript-os-x-automa...

julenx 10y ago

Announcement URL http://angularjs.blogspot.ch/2016/09/angular2-final.html http://angularjs.blogspot.ch/2016/09/angular2-final.html

mgadams3 10y ago

AngularClass's free project-based course on Angular 2 by Scott Moss has been pretty popular in the release candidate stage with 10k students so far. Will be getting updates with official release changes soon. http://courses.angularclass.com/p/angular-2-fundamentals http://courses.angularclass.com/p/angular-2-fundamentals

awjr 10y ago

Looking at https://github.com/angular/angular/milestones https://github.com/angular/angular/milestones I was slightly surprised to see 30 outstanding issues. Reading the announcement they have been careful to bring semver into the mix. This should speed up release as well as start bringing through some of the 2.1 stuff quicker.

boxctim 10y ago

"Loved by Millions" might be overstating things a bit

arc_of_descent 10y ago
Classic sales talk, huh? Devs must be in the thousands, but the users of their apps might figure in the millions :)
- h1d 10y ago
  Users don't necessarily love the underlying framework being used though.
  - softawre 10y ago
    This just in: billions love javascript!

doczoidberg 10y ago

Nodody mentioned angular universal here. I think it's a big win to prerender the SPA on the server. It's faster, more mobile friendly and pages can be indexed by search engines. IDEs have to implement better support for NG2 but this will come over time.

j_jochem 10y ago
As far as I know, Google does index SPAs that are only rendered in the browser.
- doczoidberg 10y ago
  Google does not index my ng2 site without prerendering. There will be always limits for search engines on interpreting js.
  - j_jochem 10y ago
    That's interesting. I previously researched this with regard to React apps, and the tenor was that server-side rendering was no longer required in order to get indexed by Google. Google itself has this to say: https://webmasters.googleblog.com/2014/05/understanding-web-pages-better.html https://webmasters.googleblog.com/2014/05/understanding-web-... Have you tried to figure out the cause using Search Console?
    - Bahamut 10y ago
      I have also encountered an Angular 1 app in the wild that was indexed by Google, but there are limits to the ability of their crawler - it apparently didn't follow through to other pages.

waltero 10y ago

Nice, played around with Angular 1 and 2 - Angular2 with its use of components reminded me of making front-ends with the Apache Wicket framework some time ago. This might appeal to java full stack/backend engineers that need to once in while show case a nice and shiny GUI. It my experience, the combo of Angular with Bootstrap/Font awesome works just fine for that. Very positive to have static typing through TypeScript as well. But also here I am quite biased for I never liked the concept that 'everything is just a var' ;)

ergo14 10y ago

It is interesting how people are debating here, angular this, react that... Yet there is Polymer that just works, has a great ecosystem, awesome material design support and is a breeze to work with (+ its fast too). Right now there was 2.0 announcement and new version really supports easy migration path unlike Angular 2.x.

prohor 10y ago
Polymer and Angular 2.0 seems to have a lot concepts in common and I don't fully understand why they are going to compete, given they come from the same source. But for me it seems that Polymer nowhere picked up as Angular. When it comes to performance it is great in Chrome. In other browsers not so. I hope v2 will be much better once they can get rid of the compatibility layer for other ever-green browsers.
- ergo14 10y ago
  Have you actually benchmarked polymer in a non-chrome browser? It is much faster than Angular - somewhere around React performance. Polymer is picked up by big companies already whereas "no one"(big) is using angular 2.x for now. People here seem to project a weird bubble around Angular/React. > In other browsers not so. I hope v2 will be much better once they can get rid of the compatibility layer for other ever-green browsers. Browsers get rid of it on their own - when they implement the standards, shims load when specific functionality is found or not.
  - prohor 10y ago
    I'm not comparing against Angular (which in v1 is known not to be super fast) just between browsers. I was mainly looking at https://vaadin.github.io/gwt-polymer-elements/demo/#gwt/JavaApiWidget https://vaadin.github.io/gwt-polymer-elements/demo/#gwt/Java... . It uses a lot of widgets on one page. Take a look how on loads in Chrome, Firefox, Edge (refresh to minimize network effects). I didn't go really deep in it, but first look was that lots of time was used in registering custom elements. Sure, here it is wrapped in GWT (which would be my case), but it doesn't seem to add much, rather the fact it loads all widgets from Polymer.

kabes 10y ago

Look at the weekly meeting notes: http://g.co/ng/weekly-notes http://g.co/ng/weekly-notes . So 3 days ago they were talking about an rc7 to test out and now all of the sudden we've got a final?

nagarjun 10y ago

How does the Angular CLI compare to the Ember CLI? Also, how does Angular 2 compare to Ember 2.8?

szines 10y ago
Angular CLI is actually Ember CLI under the hood. You cannot really compare these frameworks because Ember is far ahead of all. Super stable, matured, adopted the best practices, huge addon ecosystem, brilliant community, easy to learn, great documentation. Quite an obvious abd best choice. Life and development is just super easy and fast with Ember.

kensign 10y ago

Before you consider Angular 2, do yourself a favor and check out http://aurelia.io http://aurelia.io. Compare the differences and consider the trade offs with complexity vs simplicity. It's worth a consideration.

stephenhuey 10y ago
Please! The more of you that join us in Aurelia the better it will be, and I think the Angular community will benefit as well because at least they would become aware of some more best practices they could use to improve Angular.

rukenshia 10y ago

So I have never used Angular before but work with Vue. Looking at the tutorial, why is there the syntax of [(ngModel)] (equivalent would be v-model for me) and ngFor= (v-for)? Why are they different? It looks kind of unnecessary to me. I would really appreciate if someone explained it.

zygimantasdev 10y ago
[()] indicates two-way binding. If you curious you can read more in docs [1], while ngFor is just an attribute directive which changes DOM [2] [1] - https://angular.io/docs/ts/latest/guide/template-syntax.html#!#two-way-binding-with-ngmodel https://angular.io/docs/ts/latest/guide/template-syntax.html... [2] - https://angular.io/docs/ts/latest/guide/attribute-directives.html https://angular.io/docs/ts/latest/guide/attribute-directives...

KyoChunho 10y ago

It's a fantastic framework and I'm looking forward to building a ton of cool stuff with it. Though next week's announcement... Angular 2.0.1 RC 1 It's Change Log will read: * Routing has been rebuilt.. all previous versions not compatible * We decided to rename the NgModule decorator to NgYouMAD? * All Internet tutorials no longer work... Good Luck relearning!

WA 10y ago

Right now, I'm considering which works best for me. Requirements: App for Android & iPhone plus Web-based app. The most complex part is a Graph with interactions (such as highlighting a specific value). It should feel snappy, although I don't make heavy use of neither gestures nor OS-related features. Ionic 2 + Angular 2 seem to be the best choice, since I can basically write the app once and release for all three platforms. React Native has the downside that React and React Native are two different things. Be aware that there is no such thing as React Native for the web. There's something in development right now, but nothing stable. Truly native: I can't support three platforms as a single developer and I don't feel like outsourcing it. I'll go with Ionic 2 + Angular 2, although Ionic 2 still has quite a few bugs. For example, the zoom attribute on <ion-scroll> doesn't work – which is critical for my app. Sure, there are hacks and this reminds me on the discussion from the other day: https://news.ycombinator.com/item?id=12477190 https://news.ycombinator.com/item?id=12477190 Yes, it's all very hacky. But there's really no alternative I guess.

rubber_duck 10y ago
Check out nativescript, it's TS/angular 2 equivalent to React Native.

DigitalSea 10y ago

Rob Eisenberg and his nimble team beat Angular 2 to the punch all the way back in July when Aurelia final was released. Before considering Angular, considering checking out http://aurelia.io http://aurelia.io - easier to learn, no third party dependencies and great support. I applaud the Angular team for sticking it out, but I am afraid they released far too late to compete with the likes of React, Vue and so on.

rpeden 10y ago
You might be underestimating how much inertia the Angular name has in larger enterprise dev shops. They're still creating new projects in Angular 1.x, and will eventually starting using Angular 2 just because it is called Angular.
oneshoe 10y ago
I now have several Aurelia apps in production. I've also created an app in Angular (v1), and another using Ionic (v1) - which was great. But, I can't express how well Rob and his team executed on this project. Documentation could be a little better in a couple areas but this is a place where they've done extremely well also (contradiction I know - but, for example the cheat sheets are amazing and documentation is complete on most things but there are some classes that are still not documented well enough). If you want to develop in Aurelia - just the community on Gitter - they are extremely responsive and very helpful.
- stephenhuey 10y ago
  The documentation has been improving since January, and I expect there to be plenty more in a short time because for over half a year they were focused more on getting from beta to a full release. But even with the cheat sheets it felt like there was plenty to get work done because the complexity isn't so high with Aurelia - less to get confused about! And I agree about the Gitter channel being very friendly.

deleted 10y ago

[deleted]

SonicSoul 10y ago

congrats to ng-team! funny i just spent an hour yesterday upgrading to 3.0.0-rc.7 I see their quick start has been updated to use the final. https://angular.io/docs/ts/latest/quickstart.html https://angular.io/docs/ts/latest/quickstart.html <= great way to get started. agree with other comments that RxJS is a tough library to learn but I love that they used it instead of re-inventing that wheel. It is incredibly powerful and solves a lot of asynchronous programming problems. you can see all of the methods visualized with marbles here: http://rxmarbles.com/ http://rxmarbles.com/

jffry 10y ago
Surely you know that 3.0.0-rc.7 was deprecated in favor of 3.0.0-rc386, right? :-p

gravypod 10y ago

I like that they are selling the fact they have good ide support.

dschiptsov 10y ago

How many hundreds of npm dependencies in the default install? Is Leftpad included?

renke1 10y ago
Why does it matter?
- rajangdavis 10y ago
  http://www.haneycodes.net/npm-left-pad-have-we-forgotten-how-to-program/ http://www.haneycodes.net/npm-left-pad-have-we-forgotten-how... TL;DR: Left Pad is a NPM package that was removed by it's author in protest. Apparently, a ton of other packages broke as it was a major dependency across the NPM ecosystem.

scotchio 10y ago

Shameless plug: Free Getting Started Video Course on Scotch.io Getting Started with Angular 2 https://school.scotch.io/getting-started-with-angular-2 https://school.scotch.io/getting-started-with-angular-2

martyn80 10y ago

The angular website itself still uses 1.4.8? I can't find a benchmark or size comparision somewhere.

deleted 10y ago

[deleted]

electrotype 10y ago

Serious question : Why are SPA frameworks so popular these days? When someone asks "What should I use for web development?", It's now all about React/Angular/Ember/etc. But when I look at how are built the sites I like and visit frequently, I'd say 95% of them are not SPA, they are classic sites where the server generate each page (sometimes with one or two Ajax requests)! The Single Page pattern is great for desktop-like applications such as Gmail, it's obvious. But otherwise, I don't know... I think I still prefere the "feel" of classic websites.

overcast 10y ago
Prevalence of API's. One common interface to query/update from. You don't have to do both server side, and client side requests. Rather do it all client side. I've done of a few of these types, and now have moved onto mixed environments. Where most is rendered server sided, then only updates requested client side. Of course you're doing things twice for same queries.
scottmmjackson 10y ago
SPA frameworks are not all-encompassing tools for buildong all web pages. Notably, trying to SEO a SPA is frustrating at best and impossible at worst. However, in b2b use cases where SEO isn't an issue, SPA frameworks are ideal for coordinating a static-site<->dynamic-api system.
- pault 10y ago
  Server-side rendering is supported in several SPA frameworks now, and SEO is not an issue if you use it.
- quaunaut 10y ago
  Google's been indexing SPAs fine for quite awhile.
- charrondev 10y ago
  React, Angular 2, Vue 2 and some other SPA frameworks or view systems all support server-side rendering with very little coercion nowadays. That combined with google executing javascript during indexing means that SEO isn't nearly the issue it used to be.

jcadam 10y ago

Never used Angular. I was considering it for one project, but the uncertainty around the whole Angular 1/2 thing made it too risky, so I stuck with what I knew at the time (Backbone/Marionette). Tried Ember.js more recently, didn't much care for it. I think I'm just not a fan of large frameworks. Now mithril.js (http://mithril.js.org/ http://mithril.js.org/) has finally lured me away from Backbone :)

cubef 10y ago

I've been developing a large web app with ng2 and Dart since april, no framework is perfect, but this combo is a joy to work with. Did ng1 and react with JS before, react was more enjoyable but in the end it just doesn't compare. Anyway, great to see the release :)

leshow 10y ago

the website is barely functional for me, the anchor links in the documentation don't even work.

BigJeffeRonaldo 10y ago

Who cares

sctb 10y ago
Please comment civilly and substantively on HN or not at all. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

kingofhawks 10y ago

Congratulations!

nbevans 10y ago

At first I read this article title as "Angular 2 Finally Released" :)

deleted 10y ago

[deleted]

georgefrick 10y ago

As a developer who didn't care for Angular 1.x and strongly argued in favor of a simple approach for years (Backbone, etc). I've been using Angular 2 in a major enterprise project since RC1. Even with some of the headaches between RC releases; all of the reasoning behind those changes is technically sound. It's easy to write components and wire everything, and even small things like async validators are fluid and easy to implement. I'm loving it, and while the entire build system is still a bit of a dumpster fire; we're doing great on things like testing, code coverage; etc. There are a lot of problems with lazy developers hoping a blog will tell them how to do every little thing. The source code is on Github. If you can't get something working right; maybe go read the source code of the classes you are interacting with. I've found 99% of the time now that simply reading through the code gives me not only the transparency needed, but a clear path to a better solution. Kudos to them on the new forms; they're awesome.

Bahamut 10y ago
One thing that is hugely helpful that many developers don't do is read the tests for the library they use - in particular with Angular, reading the tests in the Angular codebase actually assist greatly in how to use a feature.

deleted 10y ago

[deleted]

omouse 10y ago

I heard that a particular company, Rangle, worked on AngularJS2 and from what I've heard of them they're an MVP/dev-agency so it isn't surprising to see some of the complaints here about broken backwards compatibility and bad documentation around testing. Seems few people know how to steward a free/open source software project that has lasted over 5 yrs.

Bahamut 10y ago
Rangle only created an Angular 2 successor to Batarang. They had nothing to do with core Angular 2 development. Angular 2 in beta/rc was in many ways rapid iteration on top of experimentation to get the core APIs & developer experience right. They have finally reached a stability point where they feel completely comfortable with the framework they have ended up with as a result, thus the formal release of 2.0. If you've actually paid attention to the development cycle of Angular 2, it was very fast - it turns out that Google moves much faster than most shops, which was seen in full display during alpha/beta/rc. However, that goes with the territory there, and the versioning did not lie. It is now following semver though, so we shouldn't be hearing of these problems anymore.

morsmodr 10y ago

frameworkFatigue++

alabamamike 10y ago

Thanks and congrats to the Angular2 team! We've been building on the release candidates since March, and we're happy to see the breaking changes come to an end.

chillypenguin 10y ago

I wonder what "Final" even means in this context. Google has already admitted that the Angular team uses the term "Release Candidate" to mean something completely different to how every other software company in the universe understands it. (Listen to Adventures in Angular podcast, episode 105.) A very rocky road ahead, methinks.

rochak 10y ago

Was waiting for its final release. Recently built an app using it and the documentation kept changing. Found it hard to keep up.