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

Why we chose Vue.js

about.gitlab.com

Post reply on HN
Print view View original

51–60 of 282 posts

Re: Why we chose Vue.js

#51

Post by megalomanu »

kimshibal wrote: post #13
aarpmcgee wrote: post #8

Are any companies switching from React to Vue? I'd be interested in hearing about that.

Our company migrated to vue.js, 4 months ago. Our complex app is messy with JSX, router, and new dev can't keep up with code. Now we start every new app with Vue.js. The gap between junior dev and senior dev comes closer. They can collaborate with less bugs, less problems and less time to develop.

New React projects are today much simpler, thanks to new libraries to manage state like Mobx, or efficient starter kits. So without denying the benefits you encounter with the migration to Vue.js, I think that a full rewrite of you React app in "modern React" would have been a good thing too.

Re: Why we chose Vue.js

#52

Post by octref »

blahbap wrote: post #46
octref wrote: post #42

To me Vue is a great tool for side projects. In React I found myself struggling to figure out what libs to use and keep myself up to date with them. I also hated configuring webpack. With Vue, I have officially supported libraries like vuex and vue-router which work great with Vue out of the box. vue-cli also allows me to scaffold projects with these libraries very easily. But the thing I like most about Vue is it al…

But is it use limited to side projects in your opinion?

No, it is solid for production and a lot of large Chinese companies like Alibaba, Baidu, Xiaomi, DJI use it.

Re: Why we chose Vue.js

#53

Post by wldlyinaccurate »

eberkund wrote: post #47
antarrah wrote: post #41

> He pointed out that when a major software company releases a their secret sauce, there is going to be hype. Devs think to themselves,'That company writes JS differently than me, and they are prominent and successful. Is their way of writing JS better than mine? And therefore must I adopt it?' Ahaha. No, believe me I'll not. That's ironic coming from GitLab. I mean I love that company but their front-end sucks big t…

Honest question, how do you know that it's the frontend that's slow and not the backend?

You only need to look at a DevTools timeline to see that it's the front-end which is slow: https://www.webpagetest.org/result/161021_08_XZF/

600KB of CSS, 800KB of JS... That's fine on your MBP over WiFi but on most pages it locks up the main thread on my phone for a good 5-10 seconds.

Re: Why we chose Vue.js

#54

Post by hesarenu »

kyriakos wrote: post #14
thaiphanvevo wrote: post #5

Earlier quoted context omitted.

The thing is that most React developers don't actually think React is that complex at all.

I think react has a steep initial learning curve but once you grasp the concepts it's not complicated. It is more verbose than vue though and requires more setup and boilerplate to get started.

React is very simple. You need to understand only its basic life cycle. Rest is just JavaScript.

Re: Why we chose Vue.js

#55

Post by flukus »

Is there anyone that's used Vue and knockout that would like to share the strengths/weaknesses of each? The both seem quite similar so I'd like to know if I missing out on anything by not switching.

Re: Why we chose Vue.js

#56

Post by Kiro »

Ok, so I've built stuff in Vue.js, React and Angular and I need to understand all the rage. I mean, Vue.js is just like Angular but with less features? I like that it's slimmer, don't get me wrong, but I just don't understand the "woah, Vue.js is the shit!" when we've had Angular for so long.

I put this in contrast to React where it's a completely new concept.

Re: Why we chose Vue.js

#57

Post by pjungwir »

Can anyone compare Vue with Knockout? In the early days of Angular etc I saw a lot of people saying they chose Knockout, and were much happier than with one of the heavier frameworks. I found its simplicity very appealing too, but it seems clear now that it's not a mainstream choice. It feels to me like a dead end. The last time I looked (a year ago?) the semi-official data mapping extension had lost its maintainer. So is Vue another shot at the same approach? What are the important differences?

Re: Why we chose Vue.js

#58

Post by megalomanu »

As a primarly backend dev, I'm very comfortable with React and I don't particularly want to switch to Vue.js. React says me : learn the HTML basics and then deal with abstractions (proof: React Native !). Vue.js says me : deal with HTML templates, everytime, everywhere. Although we even end to deal with HTML in React, I think it's easier for a backend dev with no front experience at all to grasp it. I showed React to a old java dev and he said that React reminded him some java web frameworks like Wicket or JSF. I guess Vue.js would have scared him.

Re: Why we chose Vue.js

#59

Post by swsieber »

antarrah wrote: post #41

> He pointed out that when a major software company releases a their secret sauce, there is going to be hype. Devs think to themselves,'That company writes JS differently than me, and they are prominent and successful. Is their way of writing JS better than mine? And therefore must I adopt it?' Ahaha. No, believe me I'll not. That's ironic coming from GitLab. I mean I love that company but their front-end sucks big t…

Isn't that more a symptom of their back end though, and not their js?

Re: Why we chose Vue.js

#60

Post by swsieber »

kentor wrote: post #48
Yaggo wrote: post #39

Earlier quoted context omitted.

So what is JSX if not DSL? (Yeah, you can use React without JSX, but still.)

You can think of it as sugar for `React.createElement()`, and some other stuff (like spread) but that's it. It's really easy to translate into javascript in your head. Why is this good? 1. Let's say I want to stick a debugger in my template or render function. How would you do it in Vue? Angular? I don't know, gotta look it up, not even sure if possible. How would you do it in React? I don't have to look anything up,…

You can totally use JSX with Vue.
Post reply on HN