News for hackers. Stuff that matters.
Re:Why we chose Vue.js over React by ggregoire on Sunday December 11, 2016 @01:35PM (#13152368)
Thank you for fixing the misleading information from this article.

I would add:

1."now you have to create 10 functions to get input from 10 inputs".

Or you can learn JavaScript:

  handleChange(event) {
    this.setState({ [event.target.name]: event.target.value })
  }
2. "Redux sounds like a synonym of verbosity, as well."

Nobody forces you to use Redux.

https://medium.com/@dan_abramov/you-might-not-need-redux-be4...

Re:Why we chose Vue.js over React by akhilcacharya on Sunday December 11, 2016 @06:16PM (#13154076)
> [event.target.name]: event.target.value

Dumb question but I've never seen this syntax before. What does it do or what is it called? (The brackets)

Re:Why we chose Vue.js over React by prodigal_erik on Sunday December 11, 2016 @06:21PM (#13154096)
Computed property names. Any expression whose value can convert to a string or symbol will work. ES6 added them:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Re:Why we chose Vue.js over React by akhilcacharya on Sunday December 11, 2016 @06:25PM (#13154128)
Excellent, thanks!
Re:Why we chose Vue.js over React by nobleach on Sunday December 11, 2016 @09:11PM (#13154998)
It's not a dumb question at all. It's relatively new, and I would implore the originator of that comment to take a different tone. It requires a newer browser or some sort of transpilation step. (You're probably already using one if you're using React)

Most of the React community has forged forward with ES6/ES2015, so learning that is definitely a part of the process.

Re:Why we chose Vue.js over React by mudetroit on Sunday December 11, 2016 @10:23PM (#13155256)
He may have chosen to use newer syntax, but the same pattern can be used without computed keys with only a tiny more code:

  var stateUpdate = {}
  stateUpdate[event.target.name] = event.target.value;
  this.setState=(stateUpdate);
I don't think there was anything necessarily wrong with his tone as he was addressing the tone of the original article.
Re:Why we chose Vue.js over React by nobleach on Monday December 12, 2016 @12:11AM (#13155704)
Telling someone, "or maybe you should learn JavaScript" is kind a really jerky way of saying, "you don't know what you're doing". I do think it was a terrible way to share knowledge. Yet it was an excellent way to say, "I know more than you".
Re:Why we chose Vue.js over React by moo360 on Monday December 12, 2016 @05:59AM (#13157205)
I agree it is rather combative, however it's also true. To claim that X pattern is a reason to not use a library when said pattern is actually an anti-pattern you've used because of lack of understanding is going to garner these kinds of reactions.
Re:Why we chose Vue.js over React by akhilcacharya on Sunday December 11, 2016 @11:52PM (#13155636)
This is exactly what I've been using for a while now, and was hoping something better already existed in ES6. Great to know there is!

FWIW, this is supported in the newest Chrome as well.