Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 2 Final Released

angular.io

Post reply on HN
Print view View original

81–90 of 452 posts

Re: Angular 2 Final Released

#81

Post by Bahamut »

petilon wrote: post #48

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: ' {{hero.name}}…

1 through 3 are false - in fact, it has been advertised by JetBrains that TypeScript with WebStorm can detect string templates when using the Component decorator in Angular 2 & the template option and parse them while doing debugging & syntax highlighting, and this was months ago.

I'm sure 4 can be solved by editors, if it hasn't been already.

Re: Angular 2 Final Released

#83

Post by namelezz »

petilon wrote: post #48

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: ' {{hero.name}}…

Can you use html-loader to load templates from external html files?

Edit: You can use external html files. Just look at their tutorial[0] using html-loader at the very end.

templateUrl: './app.component.html'

[0] - https://angular.io/docs/ts/latest/guide/webpack.html

Re: Angular 2 Final Released

#84

Post by [deleted] »

petilon wrote: post #48

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: ' {{hero.name}}…

[deleted]

Re: Angular 2 Final Released

#85

Post by Bahamut »

unknowingone wrote: post #70
Bahamut wrote: post #59

Earlier quoted context omitted.

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

From a purely pragmatic point of view, I can say that I write very little code when using react-bootstrap, can create screens quickly and the results look good. Not sure how much simpler of an API you can get. But to each their own. +1 to choice.

It's not about just simple - it's about making the right architectural choices that don't come back to bite you due to the need to make a change that brings down a house of cards from a library perspective.

ng-bootstrap avoids problematic apis such as component-based modals, and makes use of the much more natural service-based approach to allow developers maximum flexibility. If a developer prefers a component-based modal, a developer can very easily build a lightweight component on top of it. However, having poor design built into such a third party library that is meant to be used for a large variety of cases is a terrible experience for developers, speaking as a consumer and as a library maintainer.

Extensibility is the key here, and we maximize for that while keeping the library as small as possible - bloat is bad, and that shouldn't be the default in general.

Re: Angular 2 Final Released

#86

Post by robwormald »

jiggly_piff wrote: post #82

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

Because of projects like 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.

Re: Angular 2 Final Released

#87

Post by xeromal »

NhanH wrote: post #77
EugeneOZ wrote: post #39

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.

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

Re: Angular 2 Final Released

#88

Post by sajithdilshan »

petilon wrote: post #48

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: ' {{hero.name}}…

What editor are you using? I'm on IntelliJIDEA 2016.2 and it supports all first 4 items. But as for the latter 4 items, I hope those features will be available in IDEs in the future with the release of Angular 2 stable.

Re: Angular 2 Final Released

#89

Post by jbigelow76 »

jiggly_piff wrote: post #82

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/

Post reply on HN