Vue.js vs. React

Post by gunn » Sat, Aug 19, 2017, 6:00 PM UTC

spion wrote: post #128

al2o3cr wrote: post #121

Earlier quoted context omitted.

or introduce new and weird concepts to replace things that are easy, familiar and often better designed in the host language. Oddly, that's exactly how I feel about the "{condition_expression && template_evaluation}" idiom in JSX.

Personally I prefer the ternary operator in those cases, however I think do expressions will fix most of the if/else awkward stuff: https://babeljs.io/docs/plugins/transform-do-expressions/

  { do {
    if (condition_expression) {
      template_evaluation
    }
  }}

Post by peller » Sat, Aug 19, 2017, 6:02 PM UTC

pier25 wrote: post #191

ng12 wrote: post #179

Earlier quoted context omitted.

> It forces you to write loops, conditionals, etc, outside of the markup you are currently writing/reading What does this mean? I have a sneaking suspicion this is a symptom of poor separation of concerns.

It means that you can't loop where you actually need that loop and that makes reading and writing markup harder than it needs to be. https://facebook.github.io/react/docs/lists-and-keys.html Since JSX mixes logic and markup indistinguishably I'd say that's where the poor separation of concerns really is.

  const listItems = numbers.map((number) =>
    {number}
  );
  return (
    {listItems}
  );

  return (
    
      {numbers.map((num, i) => {num})}
    
  )

Post by hesarenu » Sat, Aug 19, 2017, 6:03 PM UTC

pier25 wrote: post #132

We moved away from React to Vue about 8 months ago and everyone on the team is a lot happier. First reason is we hate JSX. It forces you to write loops, conditionals, etc, outside of the markup you are currently writing/reading. It's like writing shitty PHP code without templates. It also forces you to use a lot of boilerplate like bind(), Object.keys(), etc. Another problem with React is that it only really solves o…

Post by tanguy_k » Sat, Aug 19, 2017, 6:07 PM UTC

seanwilson wrote: post #113

steinuil wrote: post #54

What's with the hate for JSX? I think handling HTML as data makes much more sense and is much more convenient than dealing with dumb templates or weird DSLs like Vue's or Angular's.

Surely the huge win for JSX is that you can type check it? I have a Typescript + Angular 1 project. The app logic feels robust as Typescript makes sure I'm using the right identifiers, variables aren't null/undefined etc. The Angular templates are a constant source of annoyance: they aren't type checked and aren't part of automatic variable renaming refactorings.

Post by madmax108 » Sat, Aug 19, 2017, 6:12 PM UTC

yunyu wrote: post #57

a13n wrote: post #46

You'll see quotes in this thread like "The demand for both React and Vue.js is growing tremendously" thrown around. It's good to check out npm install stats to get an unopinionated comparison. https://npm-stat.com/charts.html?package=react&package=vue&p... In reality, React is downloaded roughly 4-5x more than angular and 7-8x more than Vue. In August so far, React has 75% market share among these three libs. Interes…

Something worth noting is that both Angular and Vue are far more script-embed-directly-into-page friendly (mostly due to templating) compared to React. Almost all React users get it from NPM, while I would expect that the proportion of Angular or Vue users who get them from NPM is lower. I've seen a lot of projects for those two run without any build system (and anecdotally, I'm pretty sure I'm not the only one who's…