Earlier quoted context omitted.
> 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.
Yeah, the google trends don't seem to support that either: https://www.google.com/trends/explore#q=reactjs%2C%20angular...
Angular 2 Beta released
161–170 of 273 posts
Re: Angular 2 Beta released
#162I'm curious what Angular 2 is like for developers who normally write React? I hear 2 is a lot better than 1, but I'm still turned off by the amount of Angular-specific terminology, whereas most of React terminology is not necessarily React-specific.
Never understood why people liked React so much. I don't know why, but mixing javascript and HTML just looks... gross.
Re: Angular 2 Beta released
#163Re: Angular 2 Beta released
#164Re: Angular 2 Beta released
#165Congratulations 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.
http://www.ryan-williams.net/hacker-news-hiring-trends/2015/...
Re: Angular 2 Beta released
#166Congratulations 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.
Re: Angular 2 Beta released
#167Earlier quoted context omitted.
Then what do you use?
React providing a mustache-like format (like ractive.js uses) would be great - more familiar than JSX and less clumsy than createElement(). Edit response to person below (rate limit): there's no 'problem', just that mustache is still more familiar. Moving JSX into a different file doesn't change that.
Re: Angular 2 Beta released
#168Earlier quoted context omitted.
Apples to Fruit Basket comparison. React is a strict view layer, though i've seen too many instances of people trying to make it a ubiquitous framework. Angular is far wider reaching library. What exactly is your point here?
No, its not an apples to fruit basket comparison. When people talk about React they're not talking about only React, but more likely a front end app that implements React. No one is saying "oh I love writing view layers. It's way better than actually building things".
Re: Angular 2 Beta released
#169I'm curious what Angular 2 is like for developers who normally write React? I hear 2 is a lot better than 1, but I'm still turned off by the amount of Angular-specific terminology, whereas most of React terminology is not necessarily React-specific.
Never understood why people liked React so much. I don't know why, but mixing javascript and HTML just looks... gross.
But you never write HTML with JSX, that's the point. XML like syntax is just sugar that gets transformed into functions. This is not HTML. With angular you need to use string templates which cannot be easily validated by IDEs for instance. JSX syntax validation is straight forward because it's directly integrated in the language.
Re: Angular 2 Beta released
#170Server side rendering is mentioned in the post - for me, angular 1.x was a dead end because it did not run on the server (disregarding the confusion around services, factories etc, and all the horror in templating logic, debugging it etc) - can anyone give some insights into what this is like? I've previously written & been part of teams for a few non-trivial 'full stack' js apps that run both on the client and serve…
Design doc: https://docs.google.com/document/d/1q6g9UlmEZDXgrkY88AJZ6MUr...
It still seems like a WIP