Vue.js vs. React: what happened in 2017 • Hacker News Board

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

#131

Post by christophilus » Mon, Dec 25, 2017, 2:48 AM UTC

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 really enjoy ClojureScript, and haven't found it to be a ghost town at all. Reagent and re-frame + Figwheel are a killer combo. ClojureScript's JS interop is stellar.

I guess compared to the frantic pace of the JS ecosystem, the ClojureScript ecosystem does feel tiny and slow-paced. But I don't mind that.

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

#132

Post by pqdbr » Mon, Dec 25, 2017, 3:41 AM UTC

shostack wrote: post #130

wjossey wrote: post #52

Earlier quoted context omitted.

Yes, sorry for just tossing this one in there. Our product is build on top of rails 5.x, and rails has support for turbolinks. They make your server-side rendered application 'Feel' more SPA, by only refreshing the parts of the page that have actually changed upon server response. It still requires a massive payload to be sent across the wire, as well as a full render on the server, so it's not the "king of efficienc…

When would you recommend using turbo links over Vue? Or, conversely, would you recommend people not even bother with turbolinks? I'm learning Rails and haven't gotten to that stuff yet, but I'm wondering whether I should even waste my time learning them if something like Vue is just superior and just as easy to implement.

You can have both at the same time. If you want to build a SPA, go for Vue only. Build if you want to have a more traditional application and only use Vue for some views, it will work with turbolinks, you just have to use a gem to help you with the caching (turbolinks cachês the body tag to speed up the back button, and the gem clears the Vue app before the caching happens making it idempotent).

Turbolinks is amazing.

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

#133

Post by hesarenu » Mon, Dec 25, 2017, 3:45 AM UTC

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.

There is no react preferred way of state management. I have used mobx in many of my reactjs native projects.

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

#134

Post by kumarvvr » Mon, Dec 25, 2017, 3:52 AM UTC

I have spent quite a bit time into learning Angular (4/5). I am new to front-end dev, and found that the structured approach of Angular more appealing than React.

Should I continue with Angular or move on to React?

My goal is to create a data-driven website, with expressJS & PostgreSQL backend. Not very complicated, but not simple either.

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

#135

Post by RobertRoberts » Mon, Dec 25, 2017, 4:01 AM UTC

git-pull wrote: post #24

I think both of them are awesome and have great communities. Especially seeing as webpack has stabilized. If you're a startup, it's tempting for many founders to go in headfirst with a Vue or React. In my opinion, it's rarely necessary, and in the end a lot of the stuff has to be thrown out if underlying foundations change. I see it as web development's version of premature optimization. On the other hand, when I kep…

I am in the same boat you are. I've tried frameworks before that ended up being a mess later to recover from.

Also, I see Shadow DOM, proper html/js templates and future JS upgrades (modules, etc...) making React totally usesless, or either they will have to uproot themselves all over again to maintain equal performance from native systems.

As soon as I saw that rounded corners were coming to CSS, I stopped all the stupid hacks, I feel like JSX is an immature hack on top of mature tech. Eventually something else will come along and supplant it.

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

#136

Post by code_chimp » Mon, Dec 25, 2017, 4:31 AM UTC

kumarvvr wrote: post #134

I have spent quite a bit time into learning Angular (4/5). I am new to front-end dev, and found that the structured approach of Angular more appealing than React. Should I continue with Angular or move on to React? My goal is to create a data-driven website, with expressJS & PostgreSQL backend. Not very complicated, but not simple either.

IMHO, keep on the path you are on until you are really comfortable with Angular, then learn React as well.

I went the opposite direction - put up a large React/Redux codebase and now have moved on to a position that requires Angular. There is no harm in knowing more than one framework, I find that both will get the job done.

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

#137

Post by jcroll » Mon, Dec 25, 2017, 5:01 AM UTC

nikkwong wrote: post #94

apatheticonion wrote: post #79

Having used all of the big three. Am I the only one who likes and prefers Angular?

Curious—what makes you prefer angular?

Service container for one

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

#138

Post by philliphaydon » Mon, Dec 25, 2017, 5:35 AM UTC

santoriv wrote: post #129

What I find most interesting in these results is the satisfaction percentage i.e. (Used it before and would use again) / (Used it before and would use again + Used before and would not use again). - In 2016: React - 91% satisfaction Vue - 91% satisfaction Angular 2 - 65% satisfaction No framework - 65% satisfaction Ember - 50% satisfaction Angular - 40% satisfaction Backbone - 31% satisfaction - In 2017: React - 93%…

Angular 2 I would like to never use again. It’s caused far more problems than it’s solved. It requires deep knowledge to build large applications or else it will suffer performance problems.

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

#139

Post by philliphaydon » Mon, Dec 25, 2017, 5:41 AM UTC

lsdafjklsd wrote: post #76

I really don't get the love around vue... I always read the glowing sentiment and go, "Ok, I'm missing something, let me go back to the vue.js docs and see what's good" Things that are a deal breaker for me: 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 State management... I cut my teeth with Ember profess…

I can’t stand Jsx personally. Vue files with the entire component defined in 1 place and writing HTML templates... preferred for me.

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

#140

Post by kumarvvr » Mon, Dec 25, 2017, 5:51 AM UTC

code_chimp wrote: post #136

kumarvvr wrote: post #134

I have spent quite a bit time into learning Angular (4/5). I am new to front-end dev, and found that the structured approach of Angular more appealing than React. Should I continue with Angular or move on to React? My goal is to create a data-driven website, with expressJS & PostgreSQL backend. Not very complicated, but not simple either.

IMHO, keep on the path you are on until you are really comfortable with Angular, then learn React as well. I went the opposite direction - put up a large React/Redux codebase and now have moved on to a position that requires Angular. There is no harm in knowing more than one framework, I find that both will get the job done.

Thanks. I am thinking in a similar way. I guess knowing concepts is more important than any framework / library in particular.

I suppose Angular is more suited for me as it is semi-rigid in the way things have to be done. Complaints about TS eco-system are unfounded in my view as the basic building blocks for building any site, HTML templates, CSS (SASS/SCSS/LESS etc), client side scripting, etc are built in.