Live data from Hacker News

Angular 2 Final Released

angular.io

201–210 of 452 posts

Re: Angular 2 Final Released

#202
post #182
post #95

Earlier quoted context omitted.

Why not choose Vue.js? It's extremely simple, fast, easy to get started with, and very similar to Angular.

I like Vue.js, but there are no good UI frameworks such as Ionic that work with Vue for mobile apps.

Weex exists (https://github.com/alibaba/weex)

Re: Angular 2 Final Released

#203

Earlier quoted context omitted.

I can not share your experience at all. We are using React with Typescript for our projects at work and we have all common systems present (Linux, Windows, Mac). Our projects compile from Typescript to ES6 and then ES6 to ES5 through babel. All of that takes place in webpack, and it was pretty easy to setup. We also all use Visual Studio Code and it's a joy to work with. If you use something like hjs-webpack it gives…

Visual Studio has task runner explorer now as well, it's easy to setup command line tools to run automatically, either on project open or on build. I despair these days at the ridiculous number of command line tools you need to run, but once you've completely wasted 2 or 3 days of your life on these pointless things, cut and pasting command lines from setup instructions that give no indication what any of the flags a…

Do you really want to point and click around on everything all the time? Maybe read the documentation on what various flags mean when you decide to use something.

Re: Angular 2 Final Released

#204
post #87

Earlier quoted context omitted.

Obtuse error logging is my biggest problem. A lot of the times you have no idea what's going wrong.

That's a general javascript problem though as soon as you involve any third party library. Something funky going wrong when jQuery's involved? Good luck stepping through that.

Right now, some of the Angular 2 error messages are cryptic - I find it very difficult to figure out what goes wrong in tests currently with Angular 2, the only utility of some of the error messages end up being that there is an error in Angular's compilation of a component (for example).

Re: Angular 2 Final Released

#205
post #34
post #23

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 > ES…

We've been using Angular 2 for about 6 months now. Having things deprecate several times like the routing engine was annoying but that's the cost of being on the cutting edge. The side benefit is that we learned a lot about the inner workings of Angular. I agree with your annoyance with the UI libaries. It's been a PITA just to find a working datepicker. We eventually rolled our own starting with the source of an aba…

[deleted]

Re: Angular 2 Final Released

#206
post #77

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 do…

Any chance you can do a quick cons review too? Specifically comparing to the weakness of Angular 1 like bloated complexities, issue with custom directives or scope life-cycle.

They were going to re-write their router for the 3rd time. The back button's broken in some angular apps now.

Re: Angular 2 Final Released

#207
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 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/

Re: Angular 2 Final Released

#208
post #143

Earlier quoted context omitted.

Why would you consider JS to be a terrible language? It's not a requirement to use a framework to code in JS.

"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…

Es6 and typescript fixes all this.

Re: Angular 2 Final Released

#209

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

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/

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 JavaScriptJava bridge on Android, and a JavaScriptObjective 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

[2] https://www.nativescript.org/

[3] https://developer.apple.com/library/content/releasenotes/Int...

[4] http://tylergaw.com/articles/building-osx-apps-with-js

[5] http://developer.telerik.com/featured/javascript-os-x-automa...

Re: Angular 2 Final Released

#210
post #141

Earlier quoted context omitted.

Of note, Facebook's create-react-app provides an "official' opinionated approach. https://facebook.github.io/react/blog/2016/07/22/create-apps... There's even a pull request to bring typescript into the mix. https://github.com/facebookincubator/create-react-app/pull/5...

I'm just writing a first React app, and read beforehand that it was going to be difficult to choose which libraries to use, and to get them to work together, but I haven't found that to be much of an issue in practice. create-react-app set up all the build tooling, for a router the clear recommendation is react router, and for a flux implementation the clear recommendation is Redux. It feels like there's a well defin…

The sanctioned way forward for React is Flow. It's not as comprehensive as TypeScript, but there's no compilation required - Flow annotations just get stripped out. As of a couple of weeks ago it is part of create-react-app.

https://flowtype.org

Post reply on HN