Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue.js vs. React: what happened in 2017

pixeljets.com

Post reply on HN
Print view View original

111–120 of 177 posts

Re: Vue.js vs. React: what happened in 2017

#111

Post by jordache »

dmitriid wrote: post #104

The 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…

I absolutely hate that object literal style of defining a component... Terrible readability and annoying obj literal syntax to deal with...

Re: Vue.js vs. React: what happened in 2017

#112

Post by dustingetz »

moomin wrote: post #81
dustingetz wrote: post #22

I 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...

1) I didn't say that, I said good ideas trickle from research ecosystems to industry ecosystems, because legacy

2) Ruby (1995) showed no signs of explosion whatsoever, first rails had to come out (2005), and then industry had to realize that it was a good idea (Rails 3 is the first version I ever used, that was in 2009?). So that's 10-14 years. ClojureScript is 6. Give it a chance!

Re: Vue.js vs. React: what happened in 2017

#113

Post by [deleted] »

wirrbel wrote: post #102
moomin wrote: post #81

Earlier 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…

[deleted]

Re: Vue.js vs. React: what happened in 2017

#114

Post by styfle »

badbanana wrote: post #91

Having used both React (with Typescript and Redux) and the latest Vue (with es6 and Vuex) I prefer React, and I don't even use React Native. Vue is better for onboarding people more in tune with "classic" html + js development; and that's where the advantages end as far as I'm concerned. This might be a big win for some people. The way I reason about it is that React is simple, Vue is easy. When you take into account…

If anyone wants to try out React SSR + TypeScript, I have a working example here:

https://github.com/styfle/react-server-example-tsx

One of the reasons I picked up React is that views could be type checked at compile time which was not possible with Handlebars a few years ago.

I believe there is work being done to the TS language service to get type checking in other template languages at some point.

Re: Vue.js vs. React: what happened in 2017

#115

Post by kenning »

jetter wrote: post #59
spion wrote: post #38

Earlier quoted context omitted.

MobX+React would be just like Vue, but with the benefits of the larger React ecosystem and full type checking with typescript/flow, and the drawback of mandatory build tooling.

It is similar, but it will mean you get off the highway of React "preferred way" - for example, in case you start working with React Native you might have an issue of using different state management solutions for your web and mobile stack - it looks like nobody is using Mobx with RN in serious projects.

Chiming in with another "we use mobx and react native." Sorry for the overload of comments like this but I think it's perfectly fine.

Re: Vue.js vs. React: what happened in 2017

#116

Post by rmrfrmrf »

bpicolo wrote: post #109
jonreem wrote: post #98

Earlier quoted context omitted.

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.

If `do { }` syntax makes it into ES9, the whole ternary-operator-hate business will be a moot point

Re: Vue.js vs. React: what happened in 2017

#117

Post by bpicolo »

rmrfrmrf wrote: post #116
bpicolo wrote: post #109

Earlier quoted context omitted.

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.

If `do { }` syntax makes it into ES9, the whole ternary-operator-hate business will be a moot point

That's alright. I love and appreciate React too, I just prefer Vue now.

Re: Vue.js vs. React: what happened in 2017

#118

Post by yogthos »

wirrbel wrote: post #102
moomin wrote: post #81

Earlier 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…

I'm really surprised by this assessment. I've been working with ClojureScript for the past three years, and I find the ecosystem is very vibrant. ClojureScript itself has been evolving rapidly. Lately there's been a lot of focus on Js ecosystem integration allowing you to do things such as consuming NPM modules directly. The compiler itself is very efficient doing things like dead code elimination and minification out of the box.

In terms of libraries, I haven't found anything that comes close to reagent/re-frame for building complex UIs.

Meanwhile, hot code reloading with Figwheel works beautifully, and you have a REPL for running code in the browser straight from the editor.

My team is very happy with the results of building ClojureScript based applications. I'd be curious to hear why you feel that there's nothing that's worth putting in a project.

Re: Vue.js vs. React: what happened in 2017

#119

Post by yogthos »

owebmaster wrote: post #37
dustingetz wrote: post #22

I 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…

This is my reasoning too. Until someone creates a better reagent and reframe and renatal I'm gonna stick with React

What do you find missing in Reagent currently that works better in React?
Post reply on HN