I like the simplicity of React though I don't mind the Vue templating language that much either.
Sometimes I actually prefer Vue templates because with React you often see components where it's not so clear how the rendered output will look like.
Vue.js vs. React: what happened in 2017
101–110 of 177 posts
Re: Vue.js vs. React: what happened in 2017
#102I write ClojureScript A good indicator of if a technology is going to explode, is if emerging language users are excited about it, as good ideas tend to trickle down from the more advanced/research-y ecosystems which aren't as constrained by legacy. So for example React was built by a user of OCaml. ClojureScript early adopted React.js through the Om project in 2013 and there is a growing number of competing React ad…
Speaking as someone who writes ClojureScript themselves, ClojureScript is definitely in the category of technologies that show no sign of explosion whatsoever. React and Vue are both great technologies, but with Teact the template syntax is optional, and no lisp user wants another syntax...
I picked up ClojureScript at the end of 2013. I was a C++ developer then in a small firm and was tasked to write a web frontend. Outsourcing that project had failed before (2 times iirc), so my boss bet on me to do it. I knew HTML and had written probably Last year I had another look at ClojureScript and it felt like a ghost town. This saddens me. There are a few inspiring talks now and then, but nothing I found worth using in a project.
Re: Vue.js vs. React: what happened in 2017
#103It's a shame there's no first party supported Vue native library, but I suppose that's too much even for Evan.
Weex is not a part of the titular Vue project, but can be said to be the most endorsed one, and one that is the most up to date with Vue upstream development.
Re: Vue.js vs. React: what happened in 2017
#104The simple answer is in reading the chart. Look at "I've USED it before, and WOULD use it again".
React isn't just popular. It also consistently provides good developer experience. You have to compete not only against React's popularity, but also against that.
React:
- Used it, would use again: 14k
- Used it, would not use it again: 1k (7%)
Vue:
- Used it, would use again: 4.6k
- Used it, would not use it again: 454 (9.8%)
That ~3% difference in people who tried it, and didn't like it could be the difference between make it and break it when coming up against React. "I've heard about it, and I'm not interested" is another important metric.
---
Personal take:
Things I personally don't like in Vue:
- String-based programming so prevalent these days.
JSX is a thin layer on top of regular Javascript/Typescript. Where as Vue is often this:
- It breaks Javascript and how it works:
var app5 = new Vue({
el: '#app-5',
data: {
message: 'Hello Vue.js!'
},
methods: {
reverseMessage: function () {
this.message = this.message.split('').reverse().join('')
}
}
})
Re: Vue.js vs. React: what happened in 2017
#105Why in earth people would like to to use anything from facebook in they business ? Why do you trust they licensing ? I would choose riotjs or vuejs anyday before any facebook's code in my apps.
You apparently aren't keeping up with the latest about riotjs: https://github.com/riot/riot/issues/2283 I wouldn't feel confident picking that as my company's future.
Whoa. Thanks for the link, wasn't aware of that. A lesson on how not to run OSS: https://github.com/riot/riot/issues/2512
Re: Vue.js vs. React: what happened in 2017
#106Having used all of the big three. Am I the only one who likes and prefers Angular?
There are some things Angular does do far better than React IMO - Angular’s pain points are frustrating to me in terms of how I prefer to code though, largely due to its choice of supporting TS first and TS’s issues with toolchain integration/perf & not very conducive to FP, but it also has less pain in some respects such as when it comes to state.
Re: Vue.js vs. React: what happened in 2017
#107Earlier quoted context omitted.
Speaking as someone who writes ClojureScript themselves, ClojureScript is definitely in the category of technologies that show no sign of explosion whatsoever. React and Vue are both great technologies, but with Teact the template syntax is optional, and no lisp user wants another syntax...
I picked up ClojureScript at the end of 2013. I was a C++ developer then in a small firm and was tasked to write a web frontend. Outsourcing that project had failed before (2 times iirc), so my boss bet on me to do it. I knew HTML and had written probably Last year I had another look at ClojureScript and it felt like a ghost town. This saddens me. There are a few inspiring talks now and then, but nothing I found wort…
Not sure about the inspiring talks or whatnot, but I've been writing clojure/clojurescript (reagent, re-frame et al.) professionally for a couple of years and there's nothing I can't find that I need in a project. With simple js interoperability, native use of js/react components in reagent and ease of wrapping any vanilla js library, there really is nothing you can't do with clojurescript. You should take a closer look!
Re: Vue.js vs. React: what happened in 2017
#108Earlier quoted context omitted.
Why wouldn't I just use React at that point? Same behavior, less complexity.
I agree; using JSX outside React feels kinda silly. But Vue is much simpler to grok than React.
I believe React is very simple and easy to understand.
Redux is not as easy but you can go with MobX instead for easier state management.
Re: Vue.js vs. React: what happened in 2017
#109Earlier quoted context omitted.
"Template language... You can call it 'separation of concerns' all you want, but just let me generate templates using the language I already know, JSX is great" Not everyone knows JSX, so while that argument applies to you, it doesn't apply in general.
They mean javascript; jsx is a very small amount of new syntax and is embedded in normal javascript. Learning a completely separate template language with all of its own constructs for conditionals, iteration, etc. is significantly more work.
There’s not any more to learn vs html than jsx. It’s like 5 relevant constructs that all follow the same form, and the colon. Takes 20 minutes to have it down pat.
v-if is actually a big reason I prefer Vue. Ternary operators in JSX are pretty ugly. The other is that Vuex just feels so perfectly integrated. I've never felt Redux blends in particularly cleanly, though I certainly don't judge people that do prefer it.
Re: Vue.js vs. React: what happened in 2017
#110Coming from Angular, I'm biased towards entities declared in the form of a class. It's a style that is easy to manage and familiar to most programmers.
Vue currently seems to be a mix bag of styles. My take away from the little that I dabbled: - You need the vue-class-component dependency in order to declare class based components, otherwise, you're stuck with the awkward object literal notation - For state management using Vuex. You are are limited to the object literal style to declare your state store. Very awkward to work with.
Yes to get some data bound to a template and rendered out, Vue takes very little amount of code. However that is not a meaningful benefit to me. I feel Angular's complete framework and class based convention is much more suitable for a team environment.