I don't care what people say Angular totally suffers from the second system effect. http://en.wikipedia.org/wiki/Second-system_effect
> The second-system effect is the tendency of small, elegant, and successful systems to have elephantine, feature-laden monstrosities as their successors due to inflated expectations.[1] Angular 2.0 is removing a lot of complexity and "magic" of 1.x. I've moved onto React but I think it's a bit too soon to say Angular 2.0 will be a bloated monstrosity relative to 1.x.
Angular 2: Built on TypeScript
81–90 of 235 posts
Re: Angular 2: Built on TypeScript
#82First, 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 been kicking ass for a while now and making many improvements that are compelling to developers. It's a modern framework, but also easier to understand than some competitors like react.
I see the Typescript move as a positive because it shows they are at least trying to do what's right even when using tech from one of the biggest competitors. How this played internally at Google to overcome executive knee-jerk/bureaucracy/pettiness I don't know, but it's a good sign.
The community has clearly spoken, and the future of Angular is now riding on how well they absorb and react to the feedback and advances from competing teams.
Re: Angular 2: Built on TypeScript
#83Angular 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…
Re: Angular 2: Built on TypeScript
#84I don't care what people say Angular totally suffers from the second system effect. http://en.wikipedia.org/wiki/Second-system_effect
Re: Angular 2: Built on TypeScript
#85Angular 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…
Re: Angular 2: Built on TypeScript
#86Angular 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…
pun intended?
Re: Angular 2: Built on TypeScript
#87Earlier quoted context omitted.
For some reason, I doubt that people here would be complaining about learning a language that resembles the next version of Javascript if it didn't come from Microsoft.
Probably, but that's a legitimate concern. Even with Microsoft's recent open source moves (which I think are pretty awesome), we've had a history of having Microsoft force languages and extensions down our throat in an attempt to usurp the open web and standards: ActiveX, VBScript in IE, .hta's, Silverlight, etc. The counter to that is that TypeScript is Apache-licensed. However, you can't erase history by throwing u…
Re: Angular 2: Built on TypeScript
#88Earlier quoted context omitted.
I imagine they've improved the runtime size since that stack overflow post was posted a few years ago. However I've never used dart and just tried it out using a basic html sample from the tutorial page and I see: 264 Mar 5 12:21 a.dart 237K Mar 5 12:21 a.js 101K Mar 5 12:22 a.min.js It was also slow to compile, 6 secs. Anything I'm missing? https://gist.github.com/ratbeard/70902d6347ad448de0a4
If you add gzip compression, it's still smaller than doing the same thing with jQuery. "dart:html" provides an idiomatic DOM API where all list-like things are actually Lists, events are streams, Futures instead of callbacks, and so forth. It's pretty nice to use, but it's also one of the bulkier libraries. Also note that you could now add a thousand lines of code and the file size wouldn't increase much. You already…
Though as a counterpoint (and relevant to angular 2 :) I read they're going to just use the raw dom api's instead of a jquery/jquery-lite abstraction layer as the dom api's don't need the smoothing over in modern browsers like they used to.
Re: Angular 2: Built on TypeScript
#89Yay! I have tested TypeScript in hobby projects with a very positive experience. I have actually used typescript together with angular once. I was very disappointed when angular announced that they were going to make some kind of fork, for the runtime annotations they needed, instead of working together.
Re: Angular 2: Built on TypeScript
#90I like React except for JSX, since React seems to be headed in the all JSX direction I jumped ship to Polymer.
I hate the idea of having to learn a proprietary language that boils down to straight JavaScript. I hate the extra compile, I hate the lack of dubugging support. Most of all, I hate the fragmented documentation when a project has straight JavaScript examples and other examples using some abstraction.
Why is the web world doing this?