3 ms·

My impression is that a lot of "mature" (aka boring old) companies like Angular 1 and the sound of Angular 2 over React. For a number of reasons: - In general

by chvid 10y ago

My impression is that a lot of "mature" (aka boring old) companies like Angular 1 and the sound of Angular 2 over React. For a number of reasons: - In general Java and C# programmers like it. - It is made by Google (perceived as more "mature", business like) rather than Facebook (young kids). - It takes a lot of inspiration from server side development with its dependency injection and general terminology. - And TypeScript is very similar to Java and C#. (The list is a slight caricature but I hope the general point is clear.)

fchopin 10y ago
> My impression is that a lot of "mature" (aka boring old) companies like Angular 1 and the sound of Angular 2 over React. React has been around for a while, but it is still only a library. Angular 1 and 2 are frameworks. Also Angular 2 is a complete rewrite and not even in final release. I'm not sure how that is boring or old. As with Angular 1, Angular 2 aims to be opinionated, so it should be clearer how to do things than with React. Especially now with the move to components, Angular should be easier do more with, without as much confusion. And Angular 2 is much faster, if you do it right, which was one of the reasons Angular 1 was left for React. React is fine for what it is. It's somewhat "matured" for a few years and is not a bad decision if you go with it. I don't think that you should just jump on the latest JS bandwagon, but Angular 2 is more than just "for mature companies" and "similar to Java and C#". Really, the only frustration we've had with Angular 2 so far has been that it has been changing so quickly, but it's starting to settle down now.
- chvid 10y ago
  The places I am referring to are not actually using Angular 2. They are using Angular 1 but like "the sound" of Angular 2. Where the sound is the promise of a better tomorrow without actually looking at alternatives.
- bubtksins 10y ago
  > React has been around for a while, but it is still only a library. Angular 1 and 2 are frameworks. What does this even mean. Angular is also 'only a library'. > As with Angular 1, Angular 2 aims to be opinionated, so it should be clearer how to do things than with React. 'Should' and 'is' are different things, angular 1 was a complete mess. React is quite clean and straightforward. > Especially now with the move to components, Angular should be easier do more with, without as much confusion. Why? You don't give a reason of why this would be easier than with React. > And Angular 2 is much faster, if you do it right, which was one of the reasons Angular 1 was left for React. We are comparing Angular 2 with React not sure how 'Angular 2 might be better than Angular 1' is an argument against React. > React is fine for what it is. It's somewhat "matured" for a few years and is not a bad decision if you go with it. It's a much better decision than Angular 1 or Angular 2.
- dev360 10y ago
  > React has been around for a while, but it is still only a library. You probably knew this already, but worth to point out that React never intended to be a framework. This is a really interesting talk: http://2014.jsconf.eu/speakers/sebastian-markbage-minimal-api-surface-area-learning-patterns-instead-of-frameworks.html http://2014.jsconf.eu/speakers/sebastian-markbage-minimal-ap...
nothrabannosir 10y ago
> - And TypeScript is very similar to Java and C#. react and typescript go hand in hand, now that typescript has .jsx support (as .tsx files)
- nojvek 10y ago
  Typescript really has more to offer with react. It type checks the jsx(tsx), Offers code completion on components and their properties, you can refactor/rename properties and components throughout your project without side effects. Typescript is kind of blind to angular templates. React offers ability to use same code on server side and client side. Easier to test a Vdom library. It's a lot less complex, it's perf is a lot better, you can live edit. The biggest selling point is you can create native apps using native ui with a lot of code re-use. React + ts definitely give you a bigger bang for buck. I spent 2.5 years of my life writing angular code. It definitely has some good ideas but I won't be investing so much of my time in angular 2 anymore.
bubtksins 10y ago
> In general Java and C# programmers like it. Why? What are you basing this on? > It is made by Google (perceived as more "mature", business like) rather than Facebook (young kids). By who? React is more mature than angular 2 and angular 1 is crap. > It takes a lot of inspiration from server side development with its dependency injection and general terminology. I'm not sure how this is a good thing even if true. > And TypeScript is very similar to Java and C#. TypeScript can be used with React.
jpkeisala 10y ago
I totally agree on "mature" (aka boring old). I make my income on enterprise and recommending React here would be like recommending Rails over Java or C#. Meaning possibility of landing contract would be significantly lower.

by chvid 10y ago

fchopin 10y ago

> My impression is that a lot of "mature" (aka boring old) companies like Angular 1 and the sound of Angular 2 over React. React has been around for a while, but it is still only a library. Angular 1 and 2 are frameworks. Also Angular 2 is a complete rewrite and not even in final release. I'm not sure how that is boring or old. As with Angular 1, Angular 2 aims to be opinionated, so it should be clearer how to do things than with React. Especially now with the move to components, Angular should be easier do more with, without as much confusion. And Angular 2 is much faster, if you do it right, which was one of the reasons Angular 1 was left for React. React is fine for what it is. It's somewhat "matured" for a few years and is not a bad decision if you go with it. I don't think that you should just jump on the latest JS bandwagon, but Angular 2 is more than just "for mature companies" and "similar to Java and C#". Really, the only frustration we've had with Angular 2 so far has been that it has been changing so quickly, but it's starting to settle down now.

chvid 10y ago
The places I am referring to are not actually using Angular 2. They are using Angular 1 but like "the sound" of Angular 2. Where the sound is the promise of a better tomorrow without actually looking at alternatives.
bubtksins 10y ago
> React has been around for a while, but it is still only a library. Angular 1 and 2 are frameworks. What does this even mean. Angular is also 'only a library'. > As with Angular 1, Angular 2 aims to be opinionated, so it should be clearer how to do things than with React. 'Should' and 'is' are different things, angular 1 was a complete mess. React is quite clean and straightforward. > Especially now with the move to components, Angular should be easier do more with, without as much confusion. Why? You don't give a reason of why this would be easier than with React. > And Angular 2 is much faster, if you do it right, which was one of the reasons Angular 1 was left for React. We are comparing Angular 2 with React not sure how 'Angular 2 might be better than Angular 1' is an argument against React. > React is fine for what it is. It's somewhat "matured" for a few years and is not a bad decision if you go with it. It's a much better decision than Angular 1 or Angular 2.
dev360 10y ago
> React has been around for a while, but it is still only a library. You probably knew this already, but worth to point out that React never intended to be a framework. This is a really interesting talk: http://2014.jsconf.eu/speakers/sebastian-markbage-minimal-api-surface-area-learning-patterns-instead-of-frameworks.html http://2014.jsconf.eu/speakers/sebastian-markbage-minimal-ap...

nothrabannosir 10y ago

> - And TypeScript is very similar to Java and C#. react and typescript go hand in hand, now that typescript has .jsx support (as .tsx files)

nojvek 10y ago
Typescript really has more to offer with react. It type checks the jsx(tsx), Offers code completion on components and their properties, you can refactor/rename properties and components throughout your project without side effects. Typescript is kind of blind to angular templates. React offers ability to use same code on server side and client side. Easier to test a Vdom library. It's a lot less complex, it's perf is a lot better, you can live edit. The biggest selling point is you can create native apps using native ui with a lot of code re-use. React + ts definitely give you a bigger bang for buck. I spent 2.5 years of my life writing angular code. It definitely has some good ideas but I won't be investing so much of my time in angular 2 anymore.

bubtksins 10y ago

> In general Java and C# programmers like it. Why? What are you basing this on? > It is made by Google (perceived as more "mature", business like) rather than Facebook (young kids). By who? React is more mature than angular 2 and angular 1 is crap. > It takes a lot of inspiration from server side development with its dependency injection and general terminology. I'm not sure how this is a good thing even if true. > And TypeScript is very similar to Java and C#. TypeScript can be used with React.

jpkeisala 10y ago

I totally agree on "mature" (aka boring old). I make my income on enterprise and recommending React here would be like recommending Rails over Java or C#. Meaning possibility of landing contract would be significantly lower.