3 ms·

That Vue component, from a glance, seems less readable, more complex, and more stateful than the given (poorly written) React component. And none of the argumen

That Vue component, from a glance, seems less readable, more complex, and more stateful than the given (poorly written) React component. And none of the arguments against React really make sense to me (ES6 is not complicated, JSX is light syntactic sugar, and you probably don't need FLUX to start...). It seems like the _main_ problem they were having was that they were trying to graft React onto an environment based on jQuery and then realized that it made things complicated. That's not a knock against React, that's just shooting yourself in the foot and blaming the gun.

jaredcwhite 9y ago
"trying to graft React onto an environment based on jQuery" Welcome to the world of web development. Not everyone has the luxury of throwing out the last 11+ years of jQuery knowledge, plugins, tooling, etc. and building everything from scratch in React. Some people—gasp!—might have legacy codebases that they want to slowly introduce a new front-end framework into. Vue is a much better solution in both cases.
- thatswrong0 9y ago
  The problem is this article is making general statements off of their specific use case. Like this complaint: > Simple things were made harder to develop. React was created to make DOM changes fast, really fast, so you will have to use React functions to make use of this, some of which you will not be familiar with (because React has a different architectural style) It's utterly meaningless. What it really sounds like is they didn't understand React, didn't research what using React with jQuery would entail (given by the fact that they couldn't make it work), and didn't bother to learn the (relatively small) React API. React is not hard. Then this gem: > React is great, but only if you want to develop a simple application where the UI should not be consistent across different technologies Is _completely_ incorrect.. React is used at enterprise scale by many companies to develop all sorts of complex apps, and surely many of them have or had existing systems coexisting side-by-side.
tomc1985 9y ago
I've found Vue code to be the opposite, at least for my use case. It is easier to read and more in-line with naive expectations as it looks like handlebars or any other templating solution.

jaredcwhite 9y ago

"trying to graft React onto an environment based on jQuery" Welcome to the world of web development. Not everyone has the luxury of throwing out the last 11+ years of jQuery knowledge, plugins, tooling, etc. and building everything from scratch in React. Some people—gasp!—might have legacy codebases that they want to slowly introduce a new front-end framework into. Vue is a much better solution in both cases.

thatswrong0 9y ago
The problem is this article is making general statements off of their specific use case. Like this complaint: > Simple things were made harder to develop. React was created to make DOM changes fast, really fast, so you will have to use React functions to make use of this, some of which you will not be familiar with (because React has a different architectural style) It's utterly meaningless. What it really sounds like is they didn't understand React, didn't research what using React with jQuery would entail (given by the fact that they couldn't make it work), and didn't bother to learn the (relatively small) React API. React is not hard. Then this gem: > React is great, but only if you want to develop a simple application where the UI should not be consistent across different technologies Is _completely_ incorrect.. React is used at enterprise scale by many companies to develop all sorts of complex apps, and surely many of them have or had existing systems coexisting side-by-side.

tomc1985 9y ago

I've found Vue code to be the opposite, at least for my use case. It is easier to read and more in-line with naive expectations as it looks like handlebars or any other templating solution.