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

211–220 of 235 posts

Re: Angular 2: Built on TypeScript

#211

Post by robmcm »

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…

> I still have yet to see a Google website using Angular in any large capacity.

Angular is not intended for typical "websites". It's for replacing what would previously have been desktop CRUD applications. Google use it extensively for internal tooling.

It's also worth remembering that most public facing Google applications have been around for years, decades even. It would take a long time to replace one of these with Angular, even if there was a desire to do so.

Re: Angular 2: Built on TypeScript

#212

Post by VeejayRampay »

wycats wrote: post #124
coldtea wrote: post #119

Earlier quoted context omitted.

> 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?

Yep. I shipped Tokaido and people use it. It was mentioned on Ruby Weekly last week. You can get releases at https://github.com/tokaido/tokaidoapp/releases . Andres (who now maintains the project) released Tokaido for Ruby 2.1 (with support for Mavericks) recently and we're working on Ruby 2.2 support as we speak. The org is here: https://github.com/tokaido/ and there are a number of auxiliary projects (muxr and toka…

I guess you cannot say that yourself for fear of appearing to brag, but a project such as Tokaido is an EXTREMELY complicated task to tackle. So well done. And thanks for all the hours you're sinking into commercial and non-commercial projects alike, committees and everything.

Re: Angular 2: Built on TypeScript

#214

Post by jbergens »

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?

Yes, some parts are just basic structuring. Breaking an application into services, knowing what parts are singletons and not and finding ways to communicate between parts. If AtScript/TypeScript is used more you can use those skills in any project using the same language. Other parts are specific to Angular.

Re: Angular 2: Built on TypeScript

#215

Post by Keats »

ethagnawl wrote: post #198
Keats wrote: post #161

Anyone successfully using typescript with react/flux? I found it a bit cumbersome to use with most of the flux implementations

Have you tried Flow? I would (naively, perhaps) assume it was meant to work well with the rest of the FB stack.

Babel + Flow is the next combination I'm going to try

Re: Angular 2: Built on TypeScript

#216

Post by nvivo »

andrewstuart2 wrote: post #168
WhitneyLand wrote: post #82

Angular 2 is having a lot of pushback and challenges, but this may be a positive. First, there have been hard feelings over breaking backward compatibility. To rub salt in the wound the new syntax doesn't seem to buy you much for many basic scenarios. If you are going to push big breaking changes you need to show big benefits that are easy to understand at a glance. Secondly, the Ember community started small but has…

The main mistake, in my opinion, that Angular 2.0 is making is removing two-way data binding. The whole cornerstone of my love for Angular was the idea that wherever data was updated (view, model, server, another user's browser, etc.) it was trivial to make that update appear everywhere else. This is even more powerful when you add in a technology like WebRTC data channels or websockets. I could just bind the data to…

> The main mistake, in my opinion, that Angular 2.0 is making is removing two-way data binding

They talked about it in the ng-conf available on youtube. They are not removing 2-way databinding from Angular, they are just changing the way it works.

Re: Angular 2: Built on TypeScript

#217

Post by nvivo »

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 think this is more of an impression because Angular 2.0 is embracing many other things that have nothing to do with Angular, like ES6, web components, typescript.

I notice that with people trying to learn TypeScript, and see that their struggle is with classes, lambdas and modules, not with the type system that is basically the only thing TS adds to ES6.

In the end, if you look at it there is not really much to understand and all the other things you will learn anyway with Ember, React, etc. I believe most of this fear will disappear once its released.

Re: Angular 2: Built on TypeScript

#218

Post by noobhater1000 »

robmcm wrote: post #211
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…

> I still have yet to see a Google website using Angular in any large capacity. Angular is not intended for typical "websites". It's for replacing what would previously have been desktop CRUD applications. Google use it extensively for internal tooling. It's also worth remembering that most public facing Google applications have been around for years, decades even. It would take a long time to replace one of these wi…

So where is the example of why I would want to use Angular? And if it's so great Google would have transferred some of their websites over to it. I see no example of Angular being some awesome framework that inspires me to use it.

Re: Angular 2: Built on TypeScript

#219

Post by jhall1468 »

AlwaysBCoding wrote: post #150
solomone wrote: post #126

Earlier quoted context omitted.

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

Sigh... this is such an annoying comparison. If you want to compare, compare React to Angular Directives since that's a valid argument.

Your entire complaint is that full-stack front-end frameworks are bad and modular systems are good. It's great that you prefer modularity and the ability to mix and match tools.

But stop pretending React vs Angular is a thing. It isn't. git vs FTP... just stop.

Re: Angular 2: Built on TypeScript

#220

Post by jhall1468 »

WalterSear wrote: post #30
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?

- Breaking changes - Obtuse, verbose, non-performant code - Did I mention breaking changes?

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