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

91–100 of 282 posts

Re: Why we chose Vue.js

#91

Post by vladimir-y »

tracker1 wrote: post #29
greyskull wrote: post #12

There's something that irks me about incorporating logic into templates. UI development is hard enough without having to bounce between js and templates to figure out how a component is actually going to behave. I haven't used Vue or React, so this is all just my gut speaking, but at least with React all the logic is there in front of you. In my mind, if there's a loop or a conditional or whatever piece of logic that…

I just don't like the bidirectional data binding that vue seems to bring with it... I've had enough experience with this in Angular at this point to know that it's painful... then the easiest way around those issues is to use classes, and computed property getters and setters. In the end, it's just painful. React is much clearer here, but there is more of a cognitive load in getting used to it, there's less magic at…

> and computed property getters and setters

It's the exact way how it's implemented in Vue, with old fashion getters/setters and some "magic" for already defined object fields, see for details https://vuejs.org/guide/reactivity.html Vue has no digest cycle (no dirty checking), so you there is no Angular's performance issues.

Re: Why we chose Vue.js

#92

Post by [deleted] »

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

[deleted]

Re: Why we chose Vue.js

#93

Post by skc »

I hate web dev.

Yet I'm loving the experience of working with VueJS. I think alot of people feel this way. The library is just that simple and straightforward.

Re: Why we chose Vue.js

#95

Post by jsjsjsjsjsjs »

skc wrote: post #93

I hate web dev. Yet I'm loving the experience of working with VueJS. I think alot of people feel this way. The library is just that simple and straightforward.

Exactly how i feel. They maintain project perfectly as well. Issues are tackled with utmost urgency. This is what angularjs was supposed to be. VueJS is perfect (as much as software can be perfect).

Re: Why we chose Vue.js

#96

Post by vladimir-y »

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.

Great to see here an engineering approach, based on analyzing the needs and the effects of the use the tool, it's different to the usual hipsters comments extolling React and JSX to the skies.

Re: Why we chose Vue.js

#97

Post by fasouto »

mhd wrote: post #86

Just pick something , internet and build a good structure on top of it . All this jquery-level bikeshedding is nice for your ad widgets and minimalistic web apps, but it won't help me replace proper GUI toolkits. And sadly, that seems to be in demand... I'll cope with your ill-designed template language (heck, if I can cope with HTML, I can cope with anything) or your JS async abstraction du jour (promises, async awa…

>>> if I can cope with HTML, I can cope with anything

Just curious, what do you find so terrible about HTML?

Re: Why we chose Vue.js

#98

Post by danielsamuels »

tracker1 wrote: post #38
smegel wrote: post #16

Oh man, I just started learning React... https://vuejs.org/guide/comparison.html

I find the comparison to React there pretty biased, especially wrt the learning curve... JSX is a cakewalk, and OMG, oh noes, you need to know the current JS language.

Well the React guys wrote a lot of it, so..

Re: Why we chose Vue.js

#100

Post by babyrainbow »

gregmac wrote: post #11

I do very little web these days, mostly working on backend data processing, network I/O and distributed comms. A bit over a year ago, I wanted a real-time web UI to visualize some of the data I had on server-side, which I was trying to do using SignalR. I went back through some of the popular frameworks, with a pretty simple mindset of "Can I read the 'getting started', and get something basic working in about 15 min…

> it's a seriously underrated benefit.

It is not without a cost, the cost being an lack of standard ways to accomplish things. For long running projects where devs may come and go, having a standard way to do things is an incredible advantage, and will result in a much more consistent code base.

For real world front end project, this is a much more important concern, imho, than ease of picking up. For your particular use case, I agree something like Vue is a better fit.

Post reply on HN