171–180 of 273 posts
Earlier quoted context omitted.
From my understanding the two aren't mutually exclusive. From example, couldn't you use ES6 decorators and typescript in the same project?
TyoeScript supports decorators with the --enableExperimentalDecorators flag.
The only thing I haven't really seen on their 'Quick Start' and 'Guides' site is any examples that show retrieving data from an API. Are those out there and I didn't see them?
The only thing I haven't really seen on their 'Quick Start' and 'Guides' site is any examples that show retrieving data from an API. Are those out there and I didn't see them?
Earlier quoted context omitted.
This is a nice worldview but doesn't hold up to the evidence. Google has said they have something like 10k Angular 1.x apps, so they will keep on working on Angular 1. Angular 2 happening along this support is showing that they're willing to invest in the conservative route and the "burn down the libraries" route at the same time.
By level of investment, both me and the OP meant in terms of products that are key to the company's operations, and need to be continuously supported and improved . Facebook is one such app for Facebook that uses React. Instagram is one such app for Facebook that also uses React. I honestly don't know any such app for Google that uses Angular. Until that changes, there is very little incentive for the Angular team to…
I had a really painful time trying to contribute to the angular 2 project. I get the impression that the developers actively working on this are working with discussion mostly internal to Google. It's a shame, because it does seem like both a very powerful and nice approach to building SPAs that I would love to contribute to.
@estsauver while I agree that it takes some time to get into contributing into a big project like Angular 2, it is simply not true that it is "Google only" project. I'm a regular contributor (#6 in terms of no of commits: https://github.com/angular/angular/graphs/contributors ) and I don't work for Google. Angular team is bunch of great people, real pleasure to work with. I can tell you - the initial effort to start…
Maybe I just had an experience of trying to get help at a series of slow times, but it was really hard to get help with the build setup.
Earlier quoted context omitted.
Then what do you use?
Just build the dom in JS, like so: React.createElement( string/ReactClass type, [object props], [children ...] )
component = React.createFactory(MyReactComponentClass);
component(props, children);Congratulations to the Angular 2 team on shipping before Christmas. The estimate was originally somewhere around early 2016, so this is a huge deal for them to get this out before the year was up. Unfortunately, Angular 2 launched into beta too late. In the amount of time that Angular 2 has taken to get to beta, ReactJS has slaughtered the front-end market share (in a good way) and completely taken developers by stor…
> ReactJS has slaughtered the front-end market share (in a good way) and completely taken develo Do you have a citation for that? I still see tons of user land projects using angular 1.
Congratulations to the Angular 2 team on shipping before Christmas. The estimate was originally somewhere around early 2016, so this is a huge deal for them to get this out before the year was up. Unfortunately, Angular 2 launched into beta too late. In the amount of time that Angular 2 has taken to get to beta, ReactJS has slaughtered the front-end market share (in a good way) and completely taken developers by stor…
> ReactJS has slaughtered the front-end market share (in a good way) and completely taken develo Do you have a citation for that? I still see tons of user land projects using angular 1.
Unfortunately, bower does not seem to collect download stats (I assume because downloads don't go through a Bower-controlled server), and I find it very likely that react usage is strongly correlated with NPM usage. React treats bower very much as a second-class citizen, even using a separate repo for its bower repository.
Congratulations to the Angular 2 team on shipping before Christmas. The estimate was originally somewhere around early 2016, so this is a huge deal for them to get this out before the year was up. Unfortunately, Angular 2 launched into beta too late. In the amount of time that Angular 2 has taken to get to beta, ReactJS has slaughtered the front-end market share (in a good way) and completely taken developers by stor…