6 ms·

I do feel like react has won

wolco 6y ago
React won the spa crowd. Lags behind in server side frameworks adoption over Vue. React won the enterprise crowd pushing angularjs out. React hasn't won over the JQuery crowd If you do primary js it probably has. If you only do some js and other things it probably hasn't yet.
- darepublic 6y ago
  Next.js is a very decent React based SSR framework imo, and not sure vue is more popular
  - baddox 6y ago
    Gatsby is another very popular SSR framework that uses React.
    - eivarv 6y ago
      Gatsby's a static site generator, isn't it? That's different from SSR.
      - floydnoel 6y ago
        there’s an SSR plugin for Gatsby. also, Next has the option to do SSG.
    - iaml 6y ago
      There's no reason to pick gatsby over next nowadays, next can do everything gatsby can and in a sane, reusable manner.
      - andrewingram 6y ago
        I agree in the broad sense, but this isn't entirely true. Feature-wise, Next does seem like a superset of Gatsby, especially since it can support server, static and hybrid rendering models. Architecturally, Gatsby does have some advantages. They're not ones that are particularly important to me, but I don't think it's fair to ignore them: - The plugin model is more sophisticated, and there's a huge ecosystem of them which can solve most common use cases. - The ability to use a unified data graph means page invalidation and rebuilds upon data changes can be done automatically at a very granular level -- because it's possible to keep track of which pages would be affected by every piece of data. I'd add that I have issues with both, which leads me more to Next.js because it has a lower level of vendor lock-in compared to Gatsby. Anecdotally, migrating a small site from Gatsby to Next.js replaced 150 Gatsby-related imports with 10 Next.js ones.
  - rk06 6y ago
    parent is talking about servr side frameworks like laravel, django, asp.net core mvc etc. Not node.js SSR framework For those, it is much more easier to add vue as a script tag. also easier to setup Vue, compared to react.
- throwaway189262 6y ago
  So glad Angular is dying off. It looks nice on the surface but as soon as you try to do something outside the tutorial it gets nutty. React is at a great level of abstraction between code and UI framework. It reminds me of the MVC frameworks of olde, which by all accounts were great, just limited because they relied on page refresh for everything
  - pedrocx486 6y ago
    >So glad Angular is dying off. Uh, I'm gonna challenge you to give a source on that. Your comment sounds extremely biased towards React and dismissive towards Angular. None of those are dying out, I wouldn't we even say they compete directly.
    - adjkant 6y ago
      https://2019.stateofjs.com/front-end-frameworks/#front_end_frameworks_experience_ranking https://2019.stateofjs.com/front-end-frameworks/#front_end_f... Versus 2016: http://2016.stateofjs.com/2016/frontend/ http://2016.stateofjs.com/2016/frontend/ Angular is 100% fading, albeit slowly. Seems like a lot of slow moving enterprise companies are still going with it anecdotally. I'd bet on very few new projects opting for it currently, and probably near zero within 2-3 years. As to why, IMO Vue ate Angular's lunch. Single file components did everything angular's MVC wanted without all the failures like $scope and other things. React and Vue can coexist, but I think Vue and Angular are direct competition. Also see those developer surveys and the massive growth of popularity of Vue along with angular's fading.
      - pjmlp 6y ago
        That is AngularJS.
        adjkant 6y ago
        The 2019 popularity link isn't, and the technicality difference between AngularJS vs 2+ isn't incredibly relevant at this macro level when AngularJS's failures are very much a reason 2+ failed to be adopted. While it came with big changes, it's still not that significantly night and day different to act as if they aren't related. You're right that MVC no longer applies, but Vue's components still beat Angular 2+ and the dev world seems to have spoken pretty loudly about feature preference/priority, and many of those mean Vue over Angular while leaving React a bit more in its own world.
- azangru 6y ago
  > Lags behind in server side frameworks adoption What do you mean by this? Which server-side frameworks? Are you comparing Next and Nuxt?
  - danfo 6y ago
    (not GP) with React, declarative JavaScript code can result in HTML. JS -> HTML Server side frameworks (the usual favourites) have existing ways for code to result in HTML. Ruby/PHP/Java -> HTML Vue on the other hand can sit within HTML. So you can sprinkle in client-side logic in the views while still generally going with the grain of your server side framework. https://gitlab.com/gitlab-org/gitlab/-/blob/6cece3f49eb8777929b8a18a4fea1b8249bbb9df/app/views/projects/boards/components/sidebar/_labels.html.haml https://gitlab.com/gitlab-org/gitlab/-/blob/6cece3f49eb87779... See `if can?(current_user, :admin_issue, @project)` (Ruby) and `"v-if" => "issue.labels.length === 0"` (Vue)
    - debaserab2 6y ago
      Does the v-if execute on the server side?
pjmlp 6y ago
Where? Over here it is all about Angular and Vue, and this for a minority of projects. The large majority is done on SSR, CMS based infrastructure with vanilaJS.

React won the spa crowd. Lags behind in server side frameworks adoption over Vue. React won the enterprise crowd pushing angularjs out. React hasn't won over the JQuery crowd If you do primary js it probably has. If you only do some js and other things it probably hasn't yet.

darepublic 6y ago
Next.js is a very decent React based SSR framework imo, and not sure vue is more popular
- baddox 6y ago
  Gatsby is another very popular SSR framework that uses React.
  - eivarv 6y ago
    Gatsby's a static site generator, isn't it? That's different from SSR.
    - floydnoel 6y ago
      there’s an SSR plugin for Gatsby. also, Next has the option to do SSG.
  - iaml 6y ago
    There's no reason to pick gatsby over next nowadays, next can do everything gatsby can and in a sane, reusable manner.
    - andrewingram 6y ago
      I agree in the broad sense, but this isn't entirely true. Feature-wise, Next does seem like a superset of Gatsby, especially since it can support server, static and hybrid rendering models. Architecturally, Gatsby does have some advantages. They're not ones that are particularly important to me, but I don't think it's fair to ignore them: - The plugin model is more sophisticated, and there's a huge ecosystem of them which can solve most common use cases. - The ability to use a unified data graph means page invalidation and rebuilds upon data changes can be done automatically at a very granular level -- because it's possible to keep track of which pages would be affected by every piece of data. I'd add that I have issues with both, which leads me more to Next.js because it has a lower level of vendor lock-in compared to Gatsby. Anecdotally, migrating a small site from Gatsby to Next.js replaced 150 Gatsby-related imports with 10 Next.js ones.
- rk06 6y ago
  parent is talking about servr side frameworks like laravel, django, asp.net core mvc etc. Not node.js SSR framework For those, it is much more easier to add vue as a script tag. also easier to setup Vue, compared to react.
throwaway189262 6y ago
So glad Angular is dying off. It looks nice on the surface but as soon as you try to do something outside the tutorial it gets nutty. React is at a great level of abstraction between code and UI framework. It reminds me of the MVC frameworks of olde, which by all accounts were great, just limited because they relied on page refresh for everything
- pedrocx486 6y ago
  >So glad Angular is dying off. Uh, I'm gonna challenge you to give a source on that. Your comment sounds extremely biased towards React and dismissive towards Angular. None of those are dying out, I wouldn't we even say they compete directly.
  - adjkant 6y ago
    https://2019.stateofjs.com/front-end-frameworks/#front_end_frameworks_experience_ranking https://2019.stateofjs.com/front-end-frameworks/#front_end_f... Versus 2016: http://2016.stateofjs.com/2016/frontend/ http://2016.stateofjs.com/2016/frontend/ Angular is 100% fading, albeit slowly. Seems like a lot of slow moving enterprise companies are still going with it anecdotally. I'd bet on very few new projects opting for it currently, and probably near zero within 2-3 years. As to why, IMO Vue ate Angular's lunch. Single file components did everything angular's MVC wanted without all the failures like $scope and other things. React and Vue can coexist, but I think Vue and Angular are direct competition. Also see those developer surveys and the massive growth of popularity of Vue along with angular's fading.
    - pjmlp 6y ago
      That is AngularJS.
      - adjkant 6y ago
        The 2019 popularity link isn't, and the technicality difference between AngularJS vs 2+ isn't incredibly relevant at this macro level when AngularJS's failures are very much a reason 2+ failed to be adopted. While it came with big changes, it's still not that significantly night and day different to act as if they aren't related. You're right that MVC no longer applies, but Vue's components still beat Angular 2+ and the dev world seems to have spoken pretty loudly about feature preference/priority, and many of those mean Vue over Angular while leaving React a bit more in its own world.
azangru 6y ago
> Lags behind in server side frameworks adoption What do you mean by this? Which server-side frameworks? Are you comparing Next and Nuxt?
- danfo 6y ago
  (not GP) with React, declarative JavaScript code can result in HTML. JS -> HTML Server side frameworks (the usual favourites) have existing ways for code to result in HTML. Ruby/PHP/Java -> HTML Vue on the other hand can sit within HTML. So you can sprinkle in client-side logic in the views while still generally going with the grain of your server side framework. https://gitlab.com/gitlab-org/gitlab/-/blob/6cece3f49eb8777929b8a18a4fea1b8249bbb9df/app/views/projects/boards/components/sidebar/_labels.html.haml https://gitlab.com/gitlab-org/gitlab/-/blob/6cece3f49eb87779... See `if can?(current_user, :admin_issue, @project)` (Ruby) and `"v-if" => "issue.labels.length === 0"` (Vue)
  - debaserab2 6y ago
    Does the v-if execute on the server side?

pjmlp 6y ago

Where? Over here it is all about Angular and Vue, and this for a minority of projects. The large majority is done on SSR, CMS based infrastructure with vanilaJS.