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

141–150 of 235 posts

Re: Angular 2: Built on TypeScript

#141

Post by adamnemecek »

usingpond wrote: post #102
dmarg wrote: post #19

Earlier quoted context omitted.

I am pretty sure that TypeScript just adds type safety and is optional. I don't see this as a huge negative and I actually see this as a positive. Just curious, what and why are all your reasons to move away from Angular?

- Not-so-great documentation. - Lengthy learning curve. - Not concerned with performance at all (can be a nightmare on mobile devices with low RAM). - Google's history of throwing away and/or deprecating projects, (see Angular v1). - I still have yet to see a Google website using Angular in any large capacity. - Ecosystem lock-in. It tries to do a LOT of stuff, and you generally need to be doing all these things the…

> - Not concerned with performance

what are the performance issues with TS?

Re: Angular 2: Built on TypeScript

#142

Post by rxcfc »

coldtea wrote: post #119
skeeterbug wrote: post #93

"Special shout out to Yehuda Katz, who helped us design the annotation+decorator proposal which helped make this work possible." How in the world does this man keep up with all these projects? He needs to write a book on motivation.

> How in the world does this man keep up with all these projects? He needs to write a book on motivation. By dumping them mid-way and getting to the next shiny one? Anybody knows how this RoR kickstarter project finally went?

Interestingly, I was just talking to someone yesterday about how Yehuda is very good at handing off projects. When he doesn't personally finish something he started, it's because he's handed off the work to someone else who is taking it to completion. I've never seen him abandon any project.

Re: Angular 2: Built on TypeScript

#143

Post by at-fates-hands »

Firegarden wrote: post #84
aikah wrote: post #46

I don't care what people say Angular totally suffers from the second system effect. http://en.wikipedia.org/wiki/Second-system_effect

I have specifically avoided angular because I feel like it's a monster in that you are so tied to learning and understanding it's proprietary system. I too have moved directly to react. Can anyone comment on how the skills learned by learning Angular can be applied any where else?

>>> I have specifically avoided angular because I feel like it's a monster in that you are so tied to learning and understanding it's proprietary system.

I actually had to exact opposite feeling about Angular. I loved that it was a complete framework and I didn't have to mix and match several libraries to get the functionality I needed.

Having said that, I've completely soured on Angular. From the big changes coming in 2.0, to not making this backwards compatible hasn't left me with any confidence they won't do this again in future releases.

I've already moved to Ember and haven't had any issues yet.

Re: Angular 2: Built on TypeScript

#144

Post by nawitus »

hderms wrote: post #138
nawitus wrote: post #75

Earlier quoted context omitted.

You want both. Compile-time checking is necessary but not sufficient. Applications are not monoliths anymore, and web applications especially will interact with multiple other processes and services. For these you really need dynamic type checking. You can either try to do it in an ad hoc way in the application code, or building the check into the language.

are you talking about the typing of data received from outside sources?

Exactly. And even when you receive data from your "own" services that you have type definitions automatically generated for, maybe there's a version mismatch in a deployment somewhere and so on.

Re: Angular 2: Built on TypeScript

#146

Post by usingpond »

adamnemecek wrote: post #141
usingpond wrote: post #102

Earlier quoted context omitted.

- Not-so-great documentation. - Lengthy learning curve. - Not concerned with performance at all (can be a nightmare on mobile devices with low RAM). - Google's history of throwing away and/or deprecating projects, (see Angular v1). - I still have yet to see a Google website using Angular in any large capacity. - Ecosystem lock-in. It tries to do a LOT of stuff, and you generally need to be doing all these things the…

> - Not concerned with performance what are the performance issues with TS?

No, that's Angular that has the perf issues.

Re: Angular 2: Built on TypeScript

#147

Post by munificent »

taylorbuley wrote: post #2

Can anyone clarify if TypeScript usage is in place of Dart or in addition to Angular Dart?

My understanding is that TypeScript will be used in place of AtScript—the language the Angular folks created to be able to cross-compile a single codebase to both JS and Dart. JS and Dart will still be first-class supported target languages.

Re: Angular 2: Built on TypeScript

#148

Post by jonesetc »

adamnemecek wrote: post #141
usingpond wrote: post #102

Earlier quoted context omitted.

- Not-so-great documentation. - Lengthy learning curve. - Not concerned with performance at all (can be a nightmare on mobile devices with low RAM). - Google's history of throwing away and/or deprecating projects, (see Angular v1). - I still have yet to see a Google website using Angular in any large capacity. - Ecosystem lock-in. It tries to do a LOT of stuff, and you generally need to be doing all these things the…

> - Not concerned with performance what are the performance issues with TS?

I think this was a jab at Angular, not TS.

Re: Angular 2: Built on TypeScript

#149

Post by usingpond »

smrtinsert wrote: post #131
usingpond wrote: post #6

As if we didn't have enough reason to move on from Angular. Now you need to learn Typescript to contribute or grok the source files?

That's why I only use assembly. Why would I bother learning C? Now I have two problems!

You can put "C developer" on your resume, good luck shopping around "Typescript developer" experience.

Re: Angular 2: Built on TypeScript

#150

Post by AlwaysBCoding »

solomone wrote: post #126
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…

It's not like anything you build in React is going to transfer over to another framework either. In fact, I've been to a lot of React talks and people mostly ask "how do I do X" in react. The last talk I went to they spent 10 mins talking about how you might make a spinner when data is loading. I think that's the nature of any framework.

No, it's different.

React is a rendering engine, it's covers the final piece of your web app (rendering a data structure into DOM). But whatever you do to create the data structure that gets passed to React is up to you. This keeps most of your domain logic outside the context of React, you just use React to render data->DOM. So basically the API you have to learn is just Javascript, which most people know already and is easy to lookup answers to your questions.

With Angular your domain logic exists in the context of the framework. i.e. if you ng-repeat something you can't just filter that collection with Javascript you have to use an ng-filter to do it which is a special Angular construct. So the API you have to learn to manipulate data isn't just Javascript it's Angular. And how does ng-filter work? Well, you're tied to the Angular docs to figure it out. The Angular docs are of particualary poor quality so this coupling turns into a really serious problem if you're trying to be productive.

To me React vs. Angular isn't a matter of preference like Ruby vs. Python -- it's more like git vs. FTP where there is a clear right answer if you're trying to be productive in a team envrionment.

Post reply on HN