News for hackers. Stuff that matters.
Re:The State of JavaScript 2017 by aroman on Tuesday December 12, 2017 @09:57PM (#15911677)
As someone who knows react very well, is there still a reason to learn Vue? Or is the primary benefit that it's easier to learn?
Re:The State of JavaScript 2017 by jaxondu on Wednesday December 13, 2017 @03:36AM (#15912919)
Maybe for VueJS's smaller size. As for React or Vue, VueJS is simpler, easier to learn, compatible with web components, comes with default router and Vuex redux style store from the core team. So this avoid lots of learning time by new user as to which router to choose, should I learn redux or mobx etc. Typical React/Redux app is full of biolerplate, where VueX is hiding them. VueX also specify a default way of dealing with async, where's in Redux you have many options that could be confusing to new user. There is also bulitin html animation/transition support. Also web dev tools for Chrome and Firefox are from core team.
Re:The State of JavaScript 2017 by blackrice on Wednesday December 13, 2017 @02:20AM (#15912625)
There are some other benefits like styled components / scoped css available by default and officially supported libraries for routing and global state management.
Re:The State of JavaScript 2017 by tga on Wednesday December 13, 2017 @04:48AM (#15913197)
The one major thing I like about Vue is that I can use it to build widgets in an otherwise serverside app without having a JavaScript build step. All I do is link Vue directly and server-side include files containing the template and code for each component.

It is possible, but not a good option, to also use React without a build step by either skipping JSX (ugly and cumbersome to use) or by using the Babel runtime (large, not really meant for production).