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

Angular 2: Built on TypeScript

blogs.msdn.com

Post reply on HN
Print view View original

231–235 of 235 posts

Re: Angular 2: Built on TypeScript

#231

Post by WalterSear »

bceagle wrote: post #136
AlwaysBCoding wrote: post #104

Earlier quoted context omitted.

You're 100% right. Once you're in Angular-land you are completely tied to the framework. You don't think about "how can I make X in my domain happen?" you think about "how do I make X in Angular happen". This coupled with the horrific Angular docs make it really tough to justify using from a productivity standpoint. I've moved to React as well and feel it's a 10x boost in productivity because I'm constantly thinking…

This will not be the case at all with Angular2. Most of the "angular" stuff will be in annotations and your code is going to be vanilla ES6 for the most part (well, with TypeScript). So, you actually are going to have a lot more freedom to mix and max other technologies. Also, FYI, the barrier in 1.x is not that high, either. There are many integrations between Angular and other frameworks (including React, FYI).

> There are many integrations between Angular and other frameworks (including React, FYI).

IME, it's a shit show, and totally inappropriate for production code. It's the mating of wrong sized dogs in the park.

Re: Angular 2: Built on TypeScript

#232

Post by k_bx »

the_gipsy wrote: post #229
k_bx wrote: post #224

Earlier quoted context omitted.

What do you mean it's not possible to work around libraries and APIs returning nulls? That's exactly the point I made, Flow solved it. Yes, they had to write interface for all browser APIs (and it's incomplete, PRs welcome), and in places where API might return null it states that it may return it. And your code has to deal with null and non-null cases explicitly (or at least put an if). You are right though that thi…

> What do you mean it's not possible to work around libraries and APIs returning nulls? That's exactly the point I made, Flow solved it. Sorry, I had the really stupid misconception that Maybe Types could not be applied to libraries and browser APIs. So it seems like a good start, but it doesn't seem really useful if they aren't even in the basic API's descriptions: https://github.com/facebook/flow/blob/master/lib/do…

If something might return null -- feel free to make a PR with making it a Maybe type, like here:

https://github.com/facebook/flow/blob/master/lib/dom.js#L359

Re: Angular 2: Built on TypeScript

#233

Post by jhall1468 »

WalterSear wrote: post #225
jhall1468 wrote: post #220

Earlier quoted context omitted.

Because progress sucks. I still don't see why we don't continue using IE 6.

Progress is great. IMHO, Angular isn't progress, and neither is painting yourself into a corner.

According to you it isn't. And that's the fundamental problem here... opinions are like assholes, everyone has one and yours certainly isn't worth more than mine.

Re: Angular 2: Built on TypeScript

#235

Post by WalterSear »

jhall1468 wrote: post #233
WalterSear wrote: post #225

Earlier quoted context omitted.

Progress is great. IMHO, Angular isn't progress, and neither is painting yourself into a corner.

According to you it isn't. And that's the fundamental problem here... opinions are like assholes, everyone has one and yours certainly isn't worth more than mine.

I don't know about that. I contributed to protractor and have worked with members of the Angular team in the past.

Opinions maybe useless, but some opinions are more useless than others.

Post reply on HN