17 ms·

Angular 2 Beta released

418 points by javajoshw 11y ago

awqrre 11y ago
I probably will get down-voted seeing all pro-Google comments but what I don't like about frameworks like Angular is that it obfuscates HTML...
thoughtpalette 11y ago
Excited to finally start playing around with this.
revelation 11y ago
That's Google for you, having to present your exciting MVW toolkit on the crash accident of a website that is Blogspot. Right now, there is a massive cookie consent form blocking my view of the actual article.
- dubcanada 11y ago
  They own Blogspot, and you could always agree to the "massive cookie consent form" and it would go away.
  - revelation 11y ago
    At which point it's still a shit, unusable site. This isn't making me excited for your magic JS library.
    - bitmapbrother 11y ago
      Shit and unreliable? Sounds like a description of Europe and their politicians.
- danso 11y ago
  To be fair, it looks like the website itself for angular.io [0] is built on Angular, or at least a HTML framework that is not Jekyll (which is what they've used for other site documentation, including AMP [1])...so at least they're dogfooding Angular on Angular's own homepage, even when it doesn't seem needed (I didn't see many features that didn't seem to be mostly static HTML) [0] https://github.com/angular/angular.io https://github.com/angular/angular.io [1] https://github.com/ampproject/docs https://github.com/ampproject/docs
- randomguy7788 11y ago
  is that a european thing?
  - sirodoht 11y ago
    Yes. https://en.wikipedia.org/wiki/HTTP_cookie#EU_cookie_directive https://en.wikipedia.org/wiki/HTTP_cookie#EU_cookie_directiv...
  - davnicwil 11y ago
    As a European, we prefer it described as a 'poorly conceived and universally despised European law thing'
    - timrichard 11y ago
      As a Brit living within a region under the influence of the EU, I concur. A massively annoying imposition from power-tripping bureaucrats who have no idea what a stateless protocol is.
- fnordsensei 11y ago
  I've yet to run into a site that doesn't set cookies anyway. Those things seem to be there just to comply with that nonsensical law. There are even some adblock/ublock/what-have-you filters now that block those forms.
haxa 11y ago
Anyone has the experience working with NativeScript and Angular 2? How's it compared with React Native? And is there any chance this will evolve to a viable alternative to developing native apps using web technology?
- jlooper 11y ago
  Jen from Telerik DevRel here...we are working with Google to ensure that Angular 2 works great for your NativeScript apps. Please check our blogs at nativescript.org for forthcoming info on performance comparisons and how-tos. I'd encourage you to visit our getting started guide on the above web site to see how you like NativeScript!
  - aikah 11y ago
    > Angular 2 works great for your NativeScript app How is it going to work exactly ?
    - X-Istence 11y ago
      Great. It's right there in the sentence you quoted.
      - aikah 11y ago
        Great doesn't the describe the WAY it is supposed to work. I asked HOW like IN WHICH WAY.
        robwormald 11y ago
        Angular2's architecture is split in such a way that the rendering layer is separated from the application code. This allows swapping out the render layer - enables stuff like NativeScript and React Native renderers, server-side universal and running your app in a web-worker, dispatching to the main thread to render.
    - burke_holland 11y ago
interdrift 11y ago
I'm a C# developer. I have been patiently waiting for angular 2.0 with the hopes of switching my stack to TS.Node + Angular and I'm really excited about trying this!
- merpnderp 11y ago
  What will be your build workflow for TS.Node? I've never really found something that works well.
- davedx 11y ago
  I'm very impressed with the power Visual Studio Code offers for developing JS/TS projects. Do you do all of your development in the .NET flavour of Visual Studio?
  - janpieterz 11y ago
    I really wanted to start using ts in my next React app but did not find any good resources and couldn't get it off the floor. Happen to have any insight on that?
    - merpnderp 11y ago
      This happened to me. When TS came out with JSX support I immediately forked our NG 1.4 project and tried to start a port. I barely got Visual Studio working with the React TS code and quickly ran out of steam. Looks like I'll need an external build step because I could never get Visual Studio to build the React app into a single app.js file.
      - janpieterz 11y ago
        Yeah, sad really. It almost seems like Visual Studio Code is getting better support for it, which from the point of a paying VS user feels a bit off, I now switch between two editors to develop one app (VS and Atom), but would love to do everything in VS. Ah well, we'll probably need to wait.
    - 11y ago
javajoshw 11y ago
Video of the team announcing the Beta release. https://www.youtube.com/watch?v=WitNPCLSZr0 https://www.youtube.com/watch?v=WitNPCLSZr0
cdnsteve 11y ago
How many Angular folks are sticking with native ES6 and babel vs TypeScript? Angular is clearly directing folks to TypeScript. I don't want to have to use TypeScript on front-end and ES6 + Babel in Node. Trying to pick one.
- javajoshw 11y ago
  As I understand it they have most of their docs written for TypeScript but they plan to fully support ES6 and have the docs to show how to use ES6 too. I would prefer ES6, however it appears that TypeScript is a bit less verbose to write.
  - aikah 11y ago
    The big difference between TS and ES6 is dependency injection. Types can be resolved through TS types while you need to use decorators with ES6. The problem I have with decorators is that they are not officially part of ES7 spec yet, even if there is a big chance they end up in the final spec, features like ES6 modules are a proof that things can be reworked to death before being standardized.
- davedx 11y ago
  I'm finding it very difficult due to the sheer number of choices. Angular 2 supports ES5, ES6, TypeScript, and Dart. It's hard enough evaluating what our upgrade path will be from Angular 1.x, let alone which language we should end up using. I kind of have a feeling that by the time we actually need (and have the resources) to upgrade or even start mixing in Angular 2 on our project, native browser support for ES6 will be close enough to complete that we won't need a transpilation step. That might be a nice time to do the migration. Looking forward to hearing what other devs end up using.
  - grumblestumble 11y ago
    A lot of Angular 2 is optimized around using Typescript. A lot of the heavily-used Typescript features (eg. annotations) are on track for ES7, but not part of ES6.
_alexander_ 11y ago
Looks promising... But personally I dislike TS., and I know that it not required for Angular 2..., Now I prefer ES6 + babel, maybe in future I'll change my attitude to TS.
- iends 11y ago
  As somebody deciding between ES6 + Babel and TS for a project...What don't you like?
moogly 11y ago
Trying to find info on their packaging story. Last I heard the official tooling seemed to be moving off systemjs+jspm in favour of WebPack, but I don't see any clear info on this; does anyone know? We've started experimenting with systemjs and really like it (though support is a bit limited right now, plus it not really liking PhantomJS/karma), and we want to modernize our Angular 1.x app packaging/loading/bundling, but don't really want to do needless work if we have to move to another solution for Angular 2.x.
- robwormald 11y ago
  We're playing with all manner of tooling here. Our CLI (broccoli based), Webpack, SystemJS / JSPM, Rollup, etc - we'll also be focusing on HTTP/2 as we move forward.
  - scotth 11y ago
    HTTP/2 in what sense?
    - moogly 11y ago
      AIUI, with HTTP/2's multiplexing requests over a single TCP connection, the need for bundling resources might just disappear completely.
Omnipresent 11y ago
Resources for learning Angular2?
- jashmenn 11y ago
  [Shameless plug]: I've been writing a book on Angular 2 over the past few months: ng-book 2 [1]. If you want to write your first app, you can get the first chapter of our book for free. You can of course learn Angular 2 from lots of disparate blogs on the internet. There's lots of good resources. But the goal of our book is that you'll be able to learn everything, in-order, in one place. We've been keeping the book updated alongside Angular's development (though it will take us a few days to get up to the most recent beta). We've already updated the book over a dozen times, so I think you'll really like it. [1]: https://www.ng-book.com/2/ https://www.ng-book.com/2/
  - niuzeta 11y ago
    ng-book is one of the most in-depth resources that I recommend to those who want to get into angular development. I can't quite say the same for ng-book 2, as I have not yet read it, but it's definitely worth spending money on, especially when you get the updated versions on digital copy.
  - meetbryce 11y ago
    I had a positive experience with ng-book for ng1. Although I've only read about half, I found it very useful. I haven't started using ng2 yet, but if I do decide to learn it i'll be purchasing ng-book 2.
- timrichard 11y ago
  egghead.io could be worth checking out... They seem well prepared for the demand in Angular2 training : https://egghead.io/technologies/angular2 https://egghead.io/technologies/angular2
estsauver 11y ago
I had a really painful time trying to contribute to the angular 2 project. I get the impression that the developers actively working on this are working with discussion mostly internal to Google. It's a shame, because it does seem like both a very powerful and nice approach to building SPAs that I would love to contribute to.
- hockeybias 11y ago
  I don't know that its a shame as it may have saved a good deal of time and I think it all looks quite promising!
- pkozlowski_os 11y ago
  @estsauver while I agree that it takes some time to get into contributing into a big project like Angular 2, it is simply not true that it is "Google only" project. I'm a regular contributor (#6 in terms of no of commits: https://github.com/angular/angular/graphs/contributors https://github.com/angular/angular/graphs/contributors) and I don't work for Google. Angular team is bunch of great people, real pleasure to work with. I can tell you - the initial effort to start contributing pays off _very_ fast.
  - estsauver 11y ago
    The only person that actually ever replied to me on Gitter was Raganwald. Maybe I just had an experience of trying to get help at a series of slow times, but it was really hard to get help with the build setup.
- EugeneOZ 11y ago
  Welcome to chat, https://gitter.im/angular/angular https://gitter.im/angular/angular, we often talk here with ng-team members and developers who use ng2 for their projects (like me).
- hitekker 11y ago
  Curious: could you describe why it was difficult to contribute?
- 11y ago
_alexander_ 11y ago
Angular size really impressive: angular2.min.js - 568K Version 1.4.* angular.min.js - 148K File size really increased (Angular1 * 4 == Angular2), if compared with first version. Something went wrong.
- alancobb 11y ago
  Unless it has been cached (from visiting other sites), this is terrible first time user experience for those with slow connection.
  - alancobb 11y ago
    Not sure why all the down votes?!
- pkozlowski_os 11y ago
  As pointed out in the blog post shaving off bytes is one of the priorities before 1.0 release. We've got many tricks to play here, so expect those numbers to be much lower in the final release.
  - hasenj 11y ago
    Shaving? Not enough. They need a serious regiment of diet and exercise.
  - jmkni 11y ago
    What about the other dependencies? Angular 1 is a fully fledged framework, you can use it on it's own, but 2 seems to depend on rxjs, and it's also bigger. To me that seems like a step backwards.
- Bahamut 11y ago
  It is beta still - this bundles the test utils and a bunch of other stuff that will be split off closer to RC/main release time.
doczoidberg 11y ago
I recommend Angular CLI for new users: https://github.com/angular/angular-cli https://github.com/angular/angular-cli It is based on ember CLI and helps a lot scaffolding new projects.
rw2 11y ago
Uh did Angular not get the memo that people hate the new syntax and typescript? This is how you turn the most popular javascript MVC framework to nothing.
- wnevets 11y ago
  I know typescript isn't required, I'm not sure about the new syntax tho.
  - doczoidberg 11y ago
    The syntax is much better now. It is easier to understand and allows better tooling.
- pixie_ 11y ago
  If only typescript was written by facebook or google then people wouldn't hate it.
  - clessg 11y ago
    Flow was written by Facebook, yet TypeScript seems markedly more popular and well-liked. There are some who hate TypeScript because MS, and there are some who hate Flow (and React) because FB. But most of the criticism against TS has, anecdotally, been technical in nature. Edit: by popular I didn't mean that it's merely used by more people. I've clarified that.
    - pixie_ 11y ago
      I'm not talking about popularity. I'm talking about indiscriminate hate because it's connected with microsoft. C# has suffered the same stigma since the beginning.
  - lisivka 11y ago
    People hate Dart, written by Google, for same reason: it is better to stick to single language, for better ecosystem, than to fragment it. I, personally, just ignoring Dart, CoffeeScript, TypeScript, etc. Life is short.
nikon 11y ago
Anyone have an upgrade plan for 1.x? I work on a rather large Angular 1.4 codebase daily and while this is good news, I'm not sure how we'd ever upgrade to be honest.
- robwormald 11y ago
  there's a very nice strategy for this - the upgrade module allows you to run ng2 components inside of ng1 apps (or vice-versa) so you can incrementally upgrade. There's a great blog post by the Thoughtram team here : http://blog.thoughtram.io/angular/2015/10/24/upgrading-apps-to-angular-2-using-ngupgrade.html http://blog.thoughtram.io/angular/2015/10/24/upgrading-apps-...
sjclemmy 11y ago
I've just started working on an app using Angular 2 and Ionic 2.: 1. TypeScript - It's really nice to be able to use a typed version of JS, although it does feel like I'm writing C# sometimes! It supports lambda syntax / ES6 which is great. 2. Annotations seem a bit clunky, not really sure what the point of them is. 3. Absolutely love the functional reactive / RxJS stuff they've incorporated - it's going to make it VERY easy to write really powerful apps. 4. It's a million times easier to develop with than angular 1. $scope.apply anyone?
- robwormald 11y ago
  The RxJS support is definitely my favorite thing in Angular2. We have plans for all sorts of cool stuff built on top of Observables. Stay tuned.
  - Matthias247 11y ago
    Started to work on a frontend for realtime automotive networking systems in angular2. I used angular2 services which provide all (non-constant) state via Observables to the components - and I'm really pleased with the result. Totally reactive, and the implementation effort and complexity is relativly low.
- auvrw 11y ago
  > $scope.apply anyone? _.defer(scope.apply... ...re typescript, i feel like if i'm gonna use a not-script of some sort, it might as well be clojurescript or something else that's like a really-srsly-not-js rather than js-but-prettier (coffee) or js-plus-a-paradigm-grab-bag (my totally uninformed take on type)
morley 11y ago
I'm curious what Angular 2 is like for developers who normally write React? I hear 2 is a lot better than 1, but I'm still turned off by the amount of Angular-specific terminology, whereas most of React terminology is not necessarily React-specific.
- merpnderp 11y ago
  We use Angular 1.4 at work, but your reasons are exactly why I'd prefer React. It is mostly just Javascript without a lot of Angular specific conventions. At least Angular 2 looks nearly as good as React and work is planning on upgrading.
- erokar 11y ago
  Me too. Impression, admittedly only from reading about it and looking at a few code samples, is that Angular 2 is over engineered and complected, as is 1.x, which I have worked in daily for over a year. ReactJs is much more appealing these days.
  - clessg 11y ago
    I've used and followed Angular 2 somewhat over the past year. My take is that React is better for engineers familiar with JavaScript, while Angular may be more comfortable for engineers with a preference for Java/C#. I don't mean that in a bad way; it's simply been my experience that people coming from those languages love what they see of Angular 2, and are repelled by React. It's not hard to see why. This code[0] from Angular 2 would just be a function in React: @Pipe({ name: 'tempConvert' }) // The work of the pipe is handled in the tranform method with our pipe's class class TempConvertPipe implements PipeTransform { transform(value: number, args: any[]) { if(value && !isNaN(value) && args[0] === 'celsius') { var temp = (value - 32) * 5/9; var places = args[1]; return temp.toFixed(places) + ' C'; } return; } } There's also the fact that Angular is a framework, whereas React is a library. Those of us in JS land typically (but not always) prefer smaller libraries. [0] https://auth0.com/blog/2015/09/03/angular2-series-working-with-pipes/ https://auth0.com/blog/2015/09/03/angular2-series-working-wi...
tvararu 11y ago
> While you can upgrade apps in a "big bang" approach where you halt production until everything is rewritten That is some very unsound advice. I find it worthy of ridicule that it's being suggested as a possibility. The upgrade path was very necessary to address the huge amount of breaking changes.
dtm5011 11y ago
The incremental upgrade path is disappointing. Step 1: Include the Angular 2 and ng-upgrade libraries with your existing application Is anyone with a serious application actually considering this? It would have been nice to include only the pieces of Angular 2 that you actually use. Instead, we have to ship both libraries, our application code and an additional plugin down the wire? I don't see this upgrade path as a legitimate option for anyone who cares about page load times.
- Alexandervn 11y ago
  There is also ngForward, which is Angular 1 with Angular 2 syntax.
segphault 11y ago
Angular 2 addresses a lot of the serious shortcomings in Angular 1.x. The Angular 2 approach to components and encapsulation feels cleaner and less complicated than the previous mess of services, factories, and directives. Though initially skeptical of Typescript, I've found that Angular 2 really benefits from the advantages of having a coherent object model and optional type safety. Typescript never gets in the way, you can selectively use type declarations only where you want to use them. It's often helpful to leave them out while prototyping and then add them later when you want more robustness and easier debugging while you are working on writing the glue code and application logic that connects your various components. As other posters have noted, you're still saddled with a lot of the artificial complexity and odd terminology that is pervasive in Angular 1.x. There are also bits and pieces of the library ecosystem, particularly the routing engine, that are over-engineered and painful to work with in practice. But, in general, I find version 2 much more intuitive and easier to reason about than version 1.x. Key features like data binding are much saner and behave more predictably. I've never particularly liked Angular or React (my personal preference right now is for Vue or Polymer), but I think Angular 2 is a solid improvement over its predecessor. More significantly, I think the improvement is substantial enough to justify the team's decision to do a clean break.
polysaturate 11y ago
The only thing I haven't really seen on their 'Quick Start' and 'Guides' site is any examples that show retrieving data from an API. Are those out there and I didn't see them?
- robwormald 11y ago
  There's an optional Http client that uses RxJS Observables - see http://plnkr.co/edit/UQJpd5dA6x45T4PPZRWW http://plnkr.co/edit/UQJpd5dA6x45T4PPZRWW for a basic demo that also uses the `async` pipe to subscribe from the view. Of course, the native fetch API works fine too.
- robwormald 11y ago
  or a bit more interesting reactive demo searching YouTube http://plnkr.co/edit/SelQZh?p=preview http://plnkr.co/edit/SelQZh?p=preview
paublyrne 11y ago
I am in Germany and this link forces a redirect to angularjs.blogspot.de because of my location (which is a version of the blog in German, which I don't read). No simple way around this, and no link I can see to go to .com instead. That's quite frustrating.
- eterm 11y ago
  I wonder, does the .co.uk one also redirect to .de? You might find that as an already-"localised" one it doesn't redirect? http://angularjs.blogspot.co.uk/ http://angularjs.blogspot.co.uk/
  - paublyrne 11y ago
    Yeah good point! (Edit) No actually I spoke to soon. Even when the url doesn't redirect, the blog post is still in German for me! (Edit again) Must have been cached, it's in English now.
- csdigi 11y ago
  Try using this url instead: http://angularjs.blogspot.com/ncr http://angularjs.blogspot.com/ncr
  - dmit 11y ago
    ncr = No Country Redirect Previously used by google.com too, seems to be ignored now. https://support.google.com/websearch/answer/873 https://support.google.com/websearch/answer/873
- 0vermorrow 11y ago
  I am in Germany as well, and it redirects me to blogspot.de but the actual content is in english.
  - Matthias247 11y ago
    same for me
snickmy 11y ago
Angular 2 is late to the party. The user base of Angular 1.x has already moved on. I wish the success of a web framework was a bit more about the technology nature of it rather than the market adoption and hype.
- cheapsteak 11y ago
  I'm not sure if that's entirely accurate Here's a chart where you can see daily download counts for react, angular, and angular2. http://npmcharts.com/compare/angular,react,angular2 http://npmcharts.com/compare/angular,react,angular2 React does indeed have about 4x as many daily downloads, but (Angular 1 + 2)'s download counts are ~5x what they were a year ago. (iirc the ng-europe RIP Angular fiasco happened in October 2014)
  - snickmy 11y ago
    I feel people using Angular 2 are people migrating from 1.x so not quite sure if is a correct estimation adding the two values. At the same times, my comment, is based on my gut feelings, nowhere close to a reliable source :)
  - yesimahuman 11y ago
    Worth noting that the onboarding process for each framework is different. Getting started with react pushes you to npm. Angular 1 pushes you to CDN, so I'm not sure how useful this graph is. Interesting, nonetheless.
    - cheapsteak 11y ago
      That's a great point. I wonder if that would change with Angular 2
  - STRiDEX 11y ago
    I feel like many angular users are using bower and react is more likely to be used in a npm context.
- deleted 11y ago
  [deleted]
SureshG 11y ago
For those of you who are using Dart, https://github.com/ng2-dart-samples https://github.com/ng2-dart-samples has many Angular 2 demos and samples and it's pretty nice ;-)
yonibot 11y ago
When people point out that Google is behind Angular, they fail to mention that the level of investment is nowhere near that of Facebook in React. I've been loving using React. Building in components is fantastic, and it just feels like writing Javascript. That's a win in my books.
- Bahamut 11y ago
  I'm pretty sure Google has invested millions more into Angular & the ecosystem than Facebook has into React - they even have a CSM on the Angular team. Even internally the investment seems to be proving vast, as Google even has a production Angular 2 app already (during the painful alpha) & multiple teams publicly pledging to use it, which will probably grow as it becomes appropriate for Google to migrate products to Angular 2. Google has a rarified number of software products compared to Facebook - it's irrational to assume all of them will jump to their framework immediately, especially considering it was in heavy R&D the past two years & only now entering beta.
  - dvcc 11y ago
    I assume he means investment as in how much they use the product. Their two top products, Facebook and Instagram heavily use React. A bunch of Google products do use Angular, but in no way are they the primary products and that probably lends to the less fluid progression.
    - pbz 11y ago
      Google AdWords is not primary enough?!
- lewisl9029 11y ago
  This is a pretty important point to consider. If Google was as invested in Angular as Facebook was in React, they would probably have gone with a more gradual, methodical approach to improving the framework (like the Ember team did). And until that changes, there is very little stopping them from doing another mostly incompatible rewrite in a few years. As it stands, Angular 2 is closer to a completely new framework roughly inspired by Angular 1.x than a new version of Angular.
knes 11y ago
We had a look at Angular 2 at Pusher since a lot of our customers are using Angular to build app. If you want to check out a quick tutorial and see some actual working angular 2 code in action , you can go to https://blog.pusher.com/real-time-apps-angular-2/ https://blog.pusher.com/real-time-apps-angular-2/
halayli 11y ago
Any suggestions for a good material UI framework that works well with Angular 2? Unfortunately, angular's material framework only works on 1.x so far.
blisterpeanuts 11y ago
This looks pretty cool. I've just been learning about Angular 1, so I guess the thing to do is start using Angular 2 as soon as it's available and not bother with the ngForward tool? I'm looking for tools that will help me create web apps with rich client experiences. I've read the critiques of AngularJS here and it sounds like it does have some limitations, but still a very good framework for corporate web apps with moderate user base and small # of browsers.
DigitalSea 11y ago
Congratulations to the Angular 2 team on shipping before Christmas. The estimate was originally somewhere around early 2016, so this is a huge deal for them to get this out before the year was up. Unfortunately, Angular 2 launched into beta too late. In the amount of time that Angular 2 has taken to get to beta, ReactJS has slaughtered the front-end market share (in a good way) and completely taken developers by storm with its simplistic component based approach. Unlike React, Google does not really treat Angular as a first-class citizen because they have such split focus and conflicting React like library for web components called Polymer. They provide some resources, but nowhere near the amount of resources that Facebook throws behind React and React Native. Now lets talk about the fact that the Angular 2 project got off to a shaky start and I know they actually rewrote various parts from scratch more than once (hence why it took so long to reach beta, approximately 2 years). That horrible templating syntax needs to be mentioned, the decision to use square and rounded brackets for binding events/data and using things like asterisks in my opinion makes Angular 2 fall into the same trap that Angular 1 did in regards to developer accessibility. I am really loving TypeScript these days and I think the decision to support it as a first-class citizen out-of-the-box was a good one (the partnership with Microsoft definitely paid off). But with that said, I think Rob Eisenberg (of Durandal fame) beat the Angular 2 team to the punch in the small space of a year in releasing his framework Aurelia (http://aurelia.io http://aurelia.io). It is what Angular 2 should have been in my opinion. Nice syntax, convention over configuration and a breeze to use.
- debaserab2 11y ago
  > ReactJS has slaughtered the front-end market share (in a good way) and completely taken develo Do you have a citation for that? I still see tons of user land projects using angular 1.
  - joshfraser 11y ago
    I just checked Datanyze which crawls the Alexa 1m and more to see which services & libraries websites are using. They've detected 234,003 sites using Angular and 2,069 using React.
rsuelzer 11y ago
I use both react and angular. At work we lean toward angular because of the overhead of having to train design teams with no real JavaScript backgrounds how to work with jsx. That being said, I use both react and angular. Angular is a full library that solves all of my problems, even if the solution isn't what I would consider ideal. React forces me to do a lot more work to get something running as it is not a framework. It is a tradeoff of time versus flexibility.
nezo 11y ago
The whole angular.io documentation is telling me "well f*ck you vanilla JS user, go learn TypeScript and come back"
- sebak 11y ago
  Well, the angular 2 beta release blog mentions that these the docs for es5/es6 are still in the works...
danpeddle 11y ago
Server side rendering is mentioned in the post - for me, angular 1.x was a dead end because it did not run on the server (disregarding the confusion around services, factories etc, and all the horror in templating logic, debugging it etc) - can anyone give some insights into what this is like? I've previously written & been part of teams for a few non-trivial 'full stack' js apps that run both on the client and server, and react's abstraction from the DOM is perfect for such things. Wondering what the 2.x approach is here. As an aside, seems to me that the days of running JS purely in the client are coming to an end, for projects when developers can have a free hand on the tech stack.
- murz 11y ago
  https://github.com/angular/universal https://github.com/angular/universal https://github.com/angular/universal-starter https://github.com/angular/universal-starter Design doc: https://docs.google.com/document/d/1q6g9UlmEZDXgrkY88AJZ6MUrUxcnwhBGS0EXbVlYicY https://docs.google.com/document/d/1q6g9UlmEZDXgrkY88AJZ6MUr... It still seems like a WIP
noahjcz 11y ago
Maybe I'm reading wrong, but Rx.js seems to be 70k minified. Seems like a giant dependency for a mobile-focused framework...
deleted 11y ago
[deleted]
chvid 11y ago
Angular2 wants dependency injection and for that to work well it needs named interfaces and thus ends up with TypeScript as its first citizen language. This is fair choice but it shows the background of the designers of Angular and that they in some sense really don't grok JavaScript. Here is a blog from mr. Ruby-on-Rails explaining why DI is a stranger in the Ruby world: http://david.heinemeierhansson.com/2012/dependency-injection-is-not-a-virtue.html http://david.heinemeierhansson.com/2012/dependency-injection... With some parallels I think.
- mercurial 11y ago
  I'm rarely happy about DI containers, but why wouldn't you want inversion of control in Javascript? We've seen how the "let's just monkey-patch because software design is hard" approach works out: it doesn't.
Halienja 11y ago
New Project - Angular2 OR React and why?
KuhlMensch 11y ago
I've played around with Angular 2 quite a bit the last few weeks. These are my (early) views for anyone interested: * Templating syntax is intuitive after an hour or two * Decorators are great! (sidenote: Warning Babel6 decided to remove them until the spec settles down) * Typescript I'm undecided about. Its a bit of a pain to work with and tooling is still early days e.g. if you want to import a single js file/lib, you create a Type definition file (.tds) just for that. And if you don't want to document every interface in that .tds, then you can give it an "Ambient" aka "whatevs" definition. But in that case it will not be retain its semantics. * The new component router wasn't ready for prime time 2 weeks ago. I doubt that has changed. And frankly, I feel a bit uncomfortable with how magical it is. That could change though, I know allot of effort is going into it. * One of the best things is losing many of the hacky artifacts of Angular1 (pseudo-modules system, 9 types of component, config phases etc etc) * IMHO the lack of opinion built into the framework will still cause allot of foot-shooting around the globe, especially compared to Ember or Aurelia. That said, if I was going to start a large enterprise project right now, I'd SERIOUSLY consider the core being written in Angular 2 + Redux. I'd have to revisit Ember before I had that decision though, its been over two years ...

418 points by javajoshw 11y ago

I probably will get down-voted seeing all pro-Google comments but what I don't like about frameworks like Angular is that it obfuscates HTML...

thoughtpalette 11y ago

Excited to finally start playing around with this.

revelation 11y ago

That's Google for you, having to present your exciting MVW toolkit on the crash accident of a website that is Blogspot. Right now, there is a massive cookie consent form blocking my view of the actual article.

dubcanada 11y ago
They own Blogspot, and you could always agree to the "massive cookie consent form" and it would go away.
- revelation 11y ago
  At which point it's still a shit, unusable site. This isn't making me excited for your magic JS library.
  - bitmapbrother 11y ago
    Shit and unreliable? Sounds like a description of Europe and their politicians.
danso 11y ago
To be fair, it looks like the website itself for angular.io [0] is built on Angular, or at least a HTML framework that is not Jekyll (which is what they've used for other site documentation, including AMP [1])...so at least they're dogfooding Angular on Angular's own homepage, even when it doesn't seem needed (I didn't see many features that didn't seem to be mostly static HTML) [0] https://github.com/angular/angular.io https://github.com/angular/angular.io [1] https://github.com/ampproject/docs https://github.com/ampproject/docs
randomguy7788 11y ago
is that a european thing?
- sirodoht 11y ago
  Yes. https://en.wikipedia.org/wiki/HTTP_cookie#EU_cookie_directive https://en.wikipedia.org/wiki/HTTP_cookie#EU_cookie_directiv...
- davnicwil 11y ago
  As a European, we prefer it described as a 'poorly conceived and universally despised European law thing'
  - timrichard 11y ago
    As a Brit living within a region under the influence of the EU, I concur. A massively annoying imposition from power-tripping bureaucrats who have no idea what a stateless protocol is.
fnordsensei 11y ago
I've yet to run into a site that doesn't set cookies anyway. Those things seem to be there just to comply with that nonsensical law. There are even some adblock/ublock/what-have-you filters now that block those forms.

haxa 11y ago

Anyone has the experience working with NativeScript and Angular 2? How's it compared with React Native? And is there any chance this will evolve to a viable alternative to developing native apps using web technology?

jlooper 11y ago
Jen from Telerik DevRel here...we are working with Google to ensure that Angular 2 works great for your NativeScript apps. Please check our blogs at nativescript.org for forthcoming info on performance comparisons and how-tos. I'd encourage you to visit our getting started guide on the above web site to see how you like NativeScript!
- aikah 11y ago
  > Angular 2 works great for your NativeScript app How is it going to work exactly ?
  - X-Istence 11y ago
    Great. It's right there in the sentence you quoted.
    - aikah 11y ago
      Great doesn't the describe the WAY it is supposed to work. I asked HOW like IN WHICH WAY.
      - robwormald 11y ago
        Angular2's architecture is split in such a way that the rendering layer is separated from the application code. This allows swapping out the render layer - enables stuff like NativeScript and React Native renderers, server-side universal and running your app in a web-worker, dispatching to the main thread to render.
  - burke_holland 11y ago

interdrift 11y ago

I'm a C# developer. I have been patiently waiting for angular 2.0 with the hopes of switching my stack to TS.Node + Angular and I'm really excited about trying this!

merpnderp 11y ago
What will be your build workflow for TS.Node? I've never really found something that works well.
davedx 11y ago
I'm very impressed with the power Visual Studio Code offers for developing JS/TS projects. Do you do all of your development in the .NET flavour of Visual Studio?
- janpieterz 11y ago
  I really wanted to start using ts in my next React app but did not find any good resources and couldn't get it off the floor. Happen to have any insight on that?
  - merpnderp 11y ago
    This happened to me. When TS came out with JSX support I immediately forked our NG 1.4 project and tried to start a port. I barely got Visual Studio working with the React TS code and quickly ran out of steam. Looks like I'll need an external build step because I could never get Visual Studio to build the React app into a single app.js file.
    - janpieterz 11y ago
      Yeah, sad really. It almost seems like Visual Studio Code is getting better support for it, which from the point of a paying VS user feels a bit off, I now switch between two editors to develop one app (VS and Atom), but would love to do everything in VS. Ah well, we'll probably need to wait.
  - 11y ago

javajoshw 11y ago

Video of the team announcing the Beta release. https://www.youtube.com/watch?v=WitNPCLSZr0 https://www.youtube.com/watch?v=WitNPCLSZr0

cdnsteve 11y ago

How many Angular folks are sticking with native ES6 and babel vs TypeScript? Angular is clearly directing folks to TypeScript. I don't want to have to use TypeScript on front-end and ES6 + Babel in Node. Trying to pick one.

javajoshw 11y ago
As I understand it they have most of their docs written for TypeScript but they plan to fully support ES6 and have the docs to show how to use ES6 too. I would prefer ES6, however it appears that TypeScript is a bit less verbose to write.
- aikah 11y ago
  The big difference between TS and ES6 is dependency injection. Types can be resolved through TS types while you need to use decorators with ES6. The problem I have with decorators is that they are not officially part of ES7 spec yet, even if there is a big chance they end up in the final spec, features like ES6 modules are a proof that things can be reworked to death before being standardized.
davedx 11y ago
I'm finding it very difficult due to the sheer number of choices. Angular 2 supports ES5, ES6, TypeScript, and Dart. It's hard enough evaluating what our upgrade path will be from Angular 1.x, let alone which language we should end up using. I kind of have a feeling that by the time we actually need (and have the resources) to upgrade or even start mixing in Angular 2 on our project, native browser support for ES6 will be close enough to complete that we won't need a transpilation step. That might be a nice time to do the migration. Looking forward to hearing what other devs end up using.
- grumblestumble 11y ago
  A lot of Angular 2 is optimized around using Typescript. A lot of the heavily-used Typescript features (eg. annotations) are on track for ES7, but not part of ES6.

_alexander_ 11y ago

Looks promising... But personally I dislike TS., and I know that it not required for Angular 2..., Now I prefer ES6 + babel, maybe in future I'll change my attitude to TS.

iends 11y ago
As somebody deciding between ES6 + Babel and TS for a project...What don't you like?

moogly 11y ago

Trying to find info on their packaging story. Last I heard the official tooling seemed to be moving off systemjs+jspm in favour of WebPack, but I don't see any clear info on this; does anyone know? We've started experimenting with systemjs and really like it (though support is a bit limited right now, plus it not really liking PhantomJS/karma), and we want to modernize our Angular 1.x app packaging/loading/bundling, but don't really want to do needless work if we have to move to another solution for Angular 2.x.

robwormald 11y ago
We're playing with all manner of tooling here. Our CLI (broccoli based), Webpack, SystemJS / JSPM, Rollup, etc - we'll also be focusing on HTTP/2 as we move forward.
- scotth 11y ago
  HTTP/2 in what sense?
  - moogly 11y ago
    AIUI, with HTTP/2's multiplexing requests over a single TCP connection, the need for bundling resources might just disappear completely.

Omnipresent 11y ago

Resources for learning Angular2?

jashmenn 11y ago
[Shameless plug]: I've been writing a book on Angular 2 over the past few months: ng-book 2 [1]. If you want to write your first app, you can get the first chapter of our book for free. You can of course learn Angular 2 from lots of disparate blogs on the internet. There's lots of good resources. But the goal of our book is that you'll be able to learn everything, in-order, in one place. We've been keeping the book updated alongside Angular's development (though it will take us a few days to get up to the most recent beta). We've already updated the book over a dozen times, so I think you'll really like it. [1]: https://www.ng-book.com/2/ https://www.ng-book.com/2/
- niuzeta 11y ago
  ng-book is one of the most in-depth resources that I recommend to those who want to get into angular development. I can't quite say the same for ng-book 2, as I have not yet read it, but it's definitely worth spending money on, especially when you get the updated versions on digital copy.
- meetbryce 11y ago
  I had a positive experience with ng-book for ng1. Although I've only read about half, I found it very useful. I haven't started using ng2 yet, but if I do decide to learn it i'll be purchasing ng-book 2.
timrichard 11y ago
egghead.io could be worth checking out... They seem well prepared for the demand in Angular2 training : https://egghead.io/technologies/angular2 https://egghead.io/technologies/angular2

estsauver 11y ago

I had a really painful time trying to contribute to the angular 2 project. I get the impression that the developers actively working on this are working with discussion mostly internal to Google. It's a shame, because it does seem like both a very powerful and nice approach to building SPAs that I would love to contribute to.

hockeybias 11y ago
I don't know that its a shame as it may have saved a good deal of time and I think it all looks quite promising!
pkozlowski_os 11y ago
@estsauver while I agree that it takes some time to get into contributing into a big project like Angular 2, it is simply not true that it is "Google only" project. I'm a regular contributor (#6 in terms of no of commits: https://github.com/angular/angular/graphs/contributors https://github.com/angular/angular/graphs/contributors) and I don't work for Google. Angular team is bunch of great people, real pleasure to work with. I can tell you - the initial effort to start contributing pays off _very_ fast.
- estsauver 11y ago
  The only person that actually ever replied to me on Gitter was Raganwald. Maybe I just had an experience of trying to get help at a series of slow times, but it was really hard to get help with the build setup.
EugeneOZ 11y ago
Welcome to chat, https://gitter.im/angular/angular https://gitter.im/angular/angular, we often talk here with ng-team members and developers who use ng2 for their projects (like me).
hitekker 11y ago
Curious: could you describe why it was difficult to contribute?
11y ago

_alexander_ 11y ago

Angular size really impressive: angular2.min.js - 568K Version 1.4.* angular.min.js - 148K File size really increased (Angular1 * 4 == Angular2), if compared with first version. Something went wrong.

alancobb 11y ago
Unless it has been cached (from visiting other sites), this is terrible first time user experience for those with slow connection.
- alancobb 11y ago
  Not sure why all the down votes?!
pkozlowski_os 11y ago
As pointed out in the blog post shaving off bytes is one of the priorities before 1.0 release. We've got many tricks to play here, so expect those numbers to be much lower in the final release.
- hasenj 11y ago
  Shaving? Not enough. They need a serious regiment of diet and exercise.
- jmkni 11y ago
  What about the other dependencies? Angular 1 is a fully fledged framework, you can use it on it's own, but 2 seems to depend on rxjs, and it's also bigger. To me that seems like a step backwards.
Bahamut 11y ago
It is beta still - this bundles the test utils and a bunch of other stuff that will be split off closer to RC/main release time.

doczoidberg 11y ago

I recommend Angular CLI for new users: https://github.com/angular/angular-cli https://github.com/angular/angular-cli It is based on ember CLI and helps a lot scaffolding new projects.

rw2 11y ago

Uh did Angular not get the memo that people hate the new syntax and typescript? This is how you turn the most popular javascript MVC framework to nothing.

wnevets 11y ago
I know typescript isn't required, I'm not sure about the new syntax tho.
- doczoidberg 11y ago
  The syntax is much better now. It is easier to understand and allows better tooling.
pixie_ 11y ago
If only typescript was written by facebook or google then people wouldn't hate it.
- clessg 11y ago
  Flow was written by Facebook, yet TypeScript seems markedly more popular and well-liked. There are some who hate TypeScript because MS, and there are some who hate Flow (and React) because FB. But most of the criticism against TS has, anecdotally, been technical in nature. Edit: by popular I didn't mean that it's merely used by more people. I've clarified that.
  - pixie_ 11y ago
    I'm not talking about popularity. I'm talking about indiscriminate hate because it's connected with microsoft. C# has suffered the same stigma since the beginning.
- lisivka 11y ago
  People hate Dart, written by Google, for same reason: it is better to stick to single language, for better ecosystem, than to fragment it. I, personally, just ignoring Dart, CoffeeScript, TypeScript, etc. Life is short.

nikon 11y ago

Anyone have an upgrade plan for 1.x? I work on a rather large Angular 1.4 codebase daily and while this is good news, I'm not sure how we'd ever upgrade to be honest.

robwormald 11y ago
there's a very nice strategy for this - the upgrade module allows you to run ng2 components inside of ng1 apps (or vice-versa) so you can incrementally upgrade. There's a great blog post by the Thoughtram team here : http://blog.thoughtram.io/angular/2015/10/24/upgrading-apps-to-angular-2-using-ngupgrade.html http://blog.thoughtram.io/angular/2015/10/24/upgrading-apps-...

sjclemmy 11y ago

I've just started working on an app using Angular 2 and Ionic 2.: 1. TypeScript - It's really nice to be able to use a typed version of JS, although it does feel like I'm writing C# sometimes! It supports lambda syntax / ES6 which is great. 2. Annotations seem a bit clunky, not really sure what the point of them is. 3. Absolutely love the functional reactive / RxJS stuff they've incorporated - it's going to make it VERY easy to write really powerful apps. 4. It's a million times easier to develop with than angular 1. $scope.apply anyone?

robwormald 11y ago
The RxJS support is definitely my favorite thing in Angular2. We have plans for all sorts of cool stuff built on top of Observables. Stay tuned.
- Matthias247 11y ago
  Started to work on a frontend for realtime automotive networking systems in angular2. I used angular2 services which provide all (non-constant) state via Observables to the components - and I'm really pleased with the result. Totally reactive, and the implementation effort and complexity is relativly low.
auvrw 11y ago
> $scope.apply anyone? _.defer(scope.apply... ...re typescript, i feel like if i'm gonna use a not-script of some sort, it might as well be clojurescript or something else that's like a really-srsly-not-js rather than js-but-prettier (coffee) or js-plus-a-paradigm-grab-bag (my totally uninformed take on type)

morley 11y ago

I'm curious what Angular 2 is like for developers who normally write React? I hear 2 is a lot better than 1, but I'm still turned off by the amount of Angular-specific terminology, whereas most of React terminology is not necessarily React-specific.

merpnderp 11y ago
We use Angular 1.4 at work, but your reasons are exactly why I'd prefer React. It is mostly just Javascript without a lot of Angular specific conventions. At least Angular 2 looks nearly as good as React and work is planning on upgrading.
erokar 11y ago
Me too. Impression, admittedly only from reading about it and looking at a few code samples, is that Angular 2 is over engineered and complected, as is 1.x, which I have worked in daily for over a year. ReactJs is much more appealing these days.
- clessg 11y ago
  I've used and followed Angular 2 somewhat over the past year. My take is that React is better for engineers familiar with JavaScript, while Angular may be more comfortable for engineers with a preference for Java/C#. I don't mean that in a bad way; it's simply been my experience that people coming from those languages love what they see of Angular 2, and are repelled by React. It's not hard to see why. This code[0] from Angular 2 would just be a function in React: @Pipe({ name: 'tempConvert' }) // The work of the pipe is handled in the tranform method with our pipe's class class TempConvertPipe implements PipeTransform { transform(value: number, args: any[]) { if(value && !isNaN(value) && args[0] === 'celsius') { var temp = (value - 32) * 5/9; var places = args[1]; return temp.toFixed(places) + ' C'; } return; } } There's also the fact that Angular is a framework, whereas React is a library. Those of us in JS land typically (but not always) prefer smaller libraries. [0] https://auth0.com/blog/2015/09/03/angular2-series-working-with-pipes/ https://auth0.com/blog/2015/09/03/angular2-series-working-wi...

tvararu 11y ago

> While you can upgrade apps in a "big bang" approach where you halt production until everything is rewritten That is some very unsound advice. I find it worthy of ridicule that it's being suggested as a possibility. The upgrade path was very necessary to address the huge amount of breaking changes.

dtm5011 11y ago

The incremental upgrade path is disappointing. Step 1: Include the Angular 2 and ng-upgrade libraries with your existing application Is anyone with a serious application actually considering this? It would have been nice to include only the pieces of Angular 2 that you actually use. Instead, we have to ship both libraries, our application code and an additional plugin down the wire? I don't see this upgrade path as a legitimate option for anyone who cares about page load times.

Alexandervn 11y ago
There is also ngForward, which is Angular 1 with Angular 2 syntax.

segphault 11y ago

Angular 2 addresses a lot of the serious shortcomings in Angular 1.x. The Angular 2 approach to components and encapsulation feels cleaner and less complicated than the previous mess of services, factories, and directives. Though initially skeptical of Typescript, I've found that Angular 2 really benefits from the advantages of having a coherent object model and optional type safety. Typescript never gets in the way, you can selectively use type declarations only where you want to use them. It's often helpful to leave them out while prototyping and then add them later when you want more robustness and easier debugging while you are working on writing the glue code and application logic that connects your various components. As other posters have noted, you're still saddled with a lot of the artificial complexity and odd terminology that is pervasive in Angular 1.x. There are also bits and pieces of the library ecosystem, particularly the routing engine, that are over-engineered and painful to work with in practice. But, in general, I find version 2 much more intuitive and easier to reason about than version 1.x. Key features like data binding are much saner and behave more predictably. I've never particularly liked Angular or React (my personal preference right now is for Vue or Polymer), but I think Angular 2 is a solid improvement over its predecessor. More significantly, I think the improvement is substantial enough to justify the team's decision to do a clean break.

polysaturate 11y ago

The only thing I haven't really seen on their 'Quick Start' and 'Guides' site is any examples that show retrieving data from an API. Are those out there and I didn't see them?

robwormald 11y ago
There's an optional Http client that uses RxJS Observables - see http://plnkr.co/edit/UQJpd5dA6x45T4PPZRWW http://plnkr.co/edit/UQJpd5dA6x45T4PPZRWW for a basic demo that also uses the `async` pipe to subscribe from the view. Of course, the native fetch API works fine too.
robwormald 11y ago
or a bit more interesting reactive demo searching YouTube http://plnkr.co/edit/SelQZh?p=preview http://plnkr.co/edit/SelQZh?p=preview

paublyrne 11y ago

I am in Germany and this link forces a redirect to angularjs.blogspot.de because of my location (which is a version of the blog in German, which I don't read). No simple way around this, and no link I can see to go to .com instead. That's quite frustrating.

eterm 11y ago
I wonder, does the .co.uk one also redirect to .de? You might find that as an already-"localised" one it doesn't redirect? http://angularjs.blogspot.co.uk/ http://angularjs.blogspot.co.uk/
- paublyrne 11y ago
  Yeah good point! (Edit) No actually I spoke to soon. Even when the url doesn't redirect, the blog post is still in German for me! (Edit again) Must have been cached, it's in English now.
csdigi 11y ago
Try using this url instead: http://angularjs.blogspot.com/ncr http://angularjs.blogspot.com/ncr
- dmit 11y ago
  ncr = No Country Redirect Previously used by google.com too, seems to be ignored now. https://support.google.com/websearch/answer/873 https://support.google.com/websearch/answer/873
0vermorrow 11y ago
I am in Germany as well, and it redirects me to blogspot.de but the actual content is in english.
- Matthias247 11y ago
  same for me

snickmy 11y ago

Angular 2 is late to the party. The user base of Angular 1.x has already moved on. I wish the success of a web framework was a bit more about the technology nature of it rather than the market adoption and hype.

cheapsteak 11y ago
I'm not sure if that's entirely accurate Here's a chart where you can see daily download counts for react, angular, and angular2. http://npmcharts.com/compare/angular,react,angular2 http://npmcharts.com/compare/angular,react,angular2 React does indeed have about 4x as many daily downloads, but (Angular 1 + 2)'s download counts are ~5x what they were a year ago. (iirc the ng-europe RIP Angular fiasco happened in October 2014)
- snickmy 11y ago
  I feel people using Angular 2 are people migrating from 1.x so not quite sure if is a correct estimation adding the two values. At the same times, my comment, is based on my gut feelings, nowhere close to a reliable source :)
- yesimahuman 11y ago
  Worth noting that the onboarding process for each framework is different. Getting started with react pushes you to npm. Angular 1 pushes you to CDN, so I'm not sure how useful this graph is. Interesting, nonetheless.
  - cheapsteak 11y ago
    That's a great point. I wonder if that would change with Angular 2
- STRiDEX 11y ago
  I feel like many angular users are using bower and react is more likely to be used in a npm context.
deleted 11y ago
[deleted]

SureshG 11y ago

For those of you who are using Dart, https://github.com/ng2-dart-samples https://github.com/ng2-dart-samples has many Angular 2 demos and samples and it's pretty nice ;-)

yonibot 11y ago

When people point out that Google is behind Angular, they fail to mention that the level of investment is nowhere near that of Facebook in React. I've been loving using React. Building in components is fantastic, and it just feels like writing Javascript. That's a win in my books.

Bahamut 11y ago
I'm pretty sure Google has invested millions more into Angular & the ecosystem than Facebook has into React - they even have a CSM on the Angular team. Even internally the investment seems to be proving vast, as Google even has a production Angular 2 app already (during the painful alpha) & multiple teams publicly pledging to use it, which will probably grow as it becomes appropriate for Google to migrate products to Angular 2. Google has a rarified number of software products compared to Facebook - it's irrational to assume all of them will jump to their framework immediately, especially considering it was in heavy R&D the past two years & only now entering beta.
- dvcc 11y ago
  I assume he means investment as in how much they use the product. Their two top products, Facebook and Instagram heavily use React. A bunch of Google products do use Angular, but in no way are they the primary products and that probably lends to the less fluid progression.
  - pbz 11y ago
    Google AdWords is not primary enough?!
lewisl9029 11y ago
This is a pretty important point to consider. If Google was as invested in Angular as Facebook was in React, they would probably have gone with a more gradual, methodical approach to improving the framework (like the Ember team did). And until that changes, there is very little stopping them from doing another mostly incompatible rewrite in a few years. As it stands, Angular 2 is closer to a completely new framework roughly inspired by Angular 1.x than a new version of Angular.

knes 11y ago

We had a look at Angular 2 at Pusher since a lot of our customers are using Angular to build app. If you want to check out a quick tutorial and see some actual working angular 2 code in action , you can go to https://blog.pusher.com/real-time-apps-angular-2/ https://blog.pusher.com/real-time-apps-angular-2/

halayli 11y ago

Any suggestions for a good material UI framework that works well with Angular 2? Unfortunately, angular's material framework only works on 1.x so far.

blisterpeanuts 11y ago

This looks pretty cool. I've just been learning about Angular 1, so I guess the thing to do is start using Angular 2 as soon as it's available and not bother with the ngForward tool? I'm looking for tools that will help me create web apps with rich client experiences. I've read the critiques of AngularJS here and it sounds like it does have some limitations, but still a very good framework for corporate web apps with moderate user base and small # of browsers.

DigitalSea 11y ago

Congratulations to the Angular 2 team on shipping before Christmas. The estimate was originally somewhere around early 2016, so this is a huge deal for them to get this out before the year was up. Unfortunately, Angular 2 launched into beta too late. In the amount of time that Angular 2 has taken to get to beta, ReactJS has slaughtered the front-end market share (in a good way) and completely taken developers by storm with its simplistic component based approach. Unlike React, Google does not really treat Angular as a first-class citizen because they have such split focus and conflicting React like library for web components called Polymer. They provide some resources, but nowhere near the amount of resources that Facebook throws behind React and React Native. Now lets talk about the fact that the Angular 2 project got off to a shaky start and I know they actually rewrote various parts from scratch more than once (hence why it took so long to reach beta, approximately 2 years). That horrible templating syntax needs to be mentioned, the decision to use square and rounded brackets for binding events/data and using things like asterisks in my opinion makes Angular 2 fall into the same trap that Angular 1 did in regards to developer accessibility. I am really loving TypeScript these days and I think the decision to support it as a first-class citizen out-of-the-box was a good one (the partnership with Microsoft definitely paid off). But with that said, I think Rob Eisenberg (of Durandal fame) beat the Angular 2 team to the punch in the small space of a year in releasing his framework Aurelia (http://aurelia.io http://aurelia.io). It is what Angular 2 should have been in my opinion. Nice syntax, convention over configuration and a breeze to use.

debaserab2 11y ago
> ReactJS has slaughtered the front-end market share (in a good way) and completely taken develo Do you have a citation for that? I still see tons of user land projects using angular 1.
- joshfraser 11y ago
  I just checked Datanyze which crawls the Alexa 1m and more to see which services & libraries websites are using. They've detected 234,003 sites using Angular and 2,069 using React.

rsuelzer 11y ago

I use both react and angular. At work we lean toward angular because of the overhead of having to train design teams with no real JavaScript backgrounds how to work with jsx. That being said, I use both react and angular. Angular is a full library that solves all of my problems, even if the solution isn't what I would consider ideal. React forces me to do a lot more work to get something running as it is not a framework. It is a tradeoff of time versus flexibility.

nezo 11y ago

The whole angular.io documentation is telling me "well f*ck you vanilla JS user, go learn TypeScript and come back"

sebak 11y ago
Well, the angular 2 beta release blog mentions that these the docs for es5/es6 are still in the works...

danpeddle 11y ago

Server side rendering is mentioned in the post - for me, angular 1.x was a dead end because it did not run on the server (disregarding the confusion around services, factories etc, and all the horror in templating logic, debugging it etc) - can anyone give some insights into what this is like? I've previously written & been part of teams for a few non-trivial 'full stack' js apps that run both on the client and server, and react's abstraction from the DOM is perfect for such things. Wondering what the 2.x approach is here. As an aside, seems to me that the days of running JS purely in the client are coming to an end, for projects when developers can have a free hand on the tech stack.

murz 11y ago
https://github.com/angular/universal https://github.com/angular/universal https://github.com/angular/universal-starter https://github.com/angular/universal-starter Design doc: https://docs.google.com/document/d/1q6g9UlmEZDXgrkY88AJZ6MUrUxcnwhBGS0EXbVlYicY https://docs.google.com/document/d/1q6g9UlmEZDXgrkY88AJZ6MUr... It still seems like a WIP

noahjcz 11y ago

Maybe I'm reading wrong, but Rx.js seems to be 70k minified. Seems like a giant dependency for a mobile-focused framework...

deleted 11y ago

[deleted]

chvid 11y ago

Angular2 wants dependency injection and for that to work well it needs named interfaces and thus ends up with TypeScript as its first citizen language. This is fair choice but it shows the background of the designers of Angular and that they in some sense really don't grok JavaScript. Here is a blog from mr. Ruby-on-Rails explaining why DI is a stranger in the Ruby world: http://david.heinemeierhansson.com/2012/dependency-injection-is-not-a-virtue.html http://david.heinemeierhansson.com/2012/dependency-injection... With some parallels I think.

mercurial 11y ago
I'm rarely happy about DI containers, but why wouldn't you want inversion of control in Javascript? We've seen how the "let's just monkey-patch because software design is hard" approach works out: it doesn't.

Halienja 11y ago

New Project - Angular2 OR React and why?

KuhlMensch 11y ago

I've played around with Angular 2 quite a bit the last few weeks. These are my (early) views for anyone interested: * Templating syntax is intuitive after an hour or two * Decorators are great! (sidenote: Warning Babel6 decided to remove them until the spec settles down) * Typescript I'm undecided about. Its a bit of a pain to work with and tooling is still early days e.g. if you want to import a single js file/lib, you create a Type definition file (.tds) just for that. And if you don't want to document every interface in that .tds, then you can give it an "Ambient" aka "whatevs" definition. But in that case it will not be retain its semantics. * The new component router wasn't ready for prime time 2 weeks ago. I doubt that has changed. And frankly, I feel a bit uncomfortable with how magical it is. That could change though, I know allot of effort is going into it. * One of the best things is losing many of the hacky artifacts of Angular1 (pseudo-modules system, 9 types of component, config phases etc etc) * IMHO the lack of opinion built into the framework will still cause allot of foot-shooting around the globe, especially compared to Ember or Aurelia. That said, if I was going to start a large enterprise project right now, I'd SERIOUSLY consider the core being written in Angular 2 + Redux. I'd have to revisit Ember before I had that decision though, its been over two years ...