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

211–220 of 282 posts

Re: Why we chose Vue.js

#211

Post by thewhitetulip »

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…

I want to learn Angular2, but am struggling to find a good source, I want to also build real-time web UI, albeit not for visualization. The problem of documentation is very real. Thank you for the feedback on Vue! I will look at it now.

Re: Why we chose Vue.js

#212

Post by nogridbag »

linkmotif wrote: post #197
ceejayoz wrote: post #171

Earlier quoted context omitted.

> As soon as I see "el: #id" it's basically over for me. There's literally only one of those, to tell what element in the HTML to bind the root Vue instance to. Vue doesn't require thinking about the DOM. It's the same sort of thing as React's basic tutorial ( https://facebook.github.io/react/docs/getting-started.html ) ReactDOM.render( Hello, world! , document.getElementById('example') );

PS. What if you're the kind of person who likes coupling presentation and logic? I really like JSX and inline styles. From my skimming, it appears Vue separates templates and logic. Is that correct?

On the contrary, for most larger apps you'll want to use single file components + webpack. I'm also a big fan of keeping markup, styles, and logic close together and Vue's single file components are one of my favorite features compared to React components:

http://vuejs.org/guide/single-file-components.html

The only downside is that while .vue files do have editor support in most editors, it's still not 100%. For example there are two plugins for VS Code but neither of them are really usable at this time.

Re: Why we chose Vue.js

#213

Post by catshirt »

burger_moon wrote: post #192
49531 wrote: post #154

I actually interviewed with Jacob Schatz when he was trying to figure out which frontend framework to use for GitLab. I had been working in React for the last year or so which was apparent on my resume. He prefaced our interview with something to the effect of "I know you do a lot of React but we are not going to ever use React at GitLab" It was weird. I tried to ascertain his reasoning and pretty much all I got was…

I recently interviewed with him and did a collab code thing and he personally admitted to being quite rusty as he doesn't write code much anymore and it was apparent by the errors he was making. I'm surprised he was the one leading the decision in what framework to use when the extent of skills seems to cut off around jQuery. Is it normal in a large company for someone who is now doing managerial type work to be the…

it's not uncommon. someone has to make a decision and it makes sense early managers are not best suited to make technical decisions.

as a company or application grows technical deficiencies resulting from bad choices will start to rear their heads and new hires with more experience will hopefully illuminate those issues.

the only reason they chose vue, the article suggests, is because it's "simple". even if I concede that to be true, it is not the most important factor when making technical decisions and you will ultimately end up paying for it.

Re: Why we chose Vue.js

#214

Post by mambodog »

askmike wrote: post #196
hesarenu wrote: post #54

Earlier quoted context omitted.

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

I disagree as soon as you write more than a single nested child/parent component, that requires a different way of thinking (should I use state or props?). And that you can't "just uses react". You kind of have to use redux (or similar) as well as a bunch of other stuff.

People keep saying you 'have to use redux' but I think that's hugely misleading to a large section of potential React users who don't need the highly complex state management that redux facilitates, and could get by just fine with setState+props.

I'd hope that people who are being exposed to this idea at least also get the chance to read 'You Might Not Need Redux': https://medium.com/@dan_abramov/you-might-not-need-redux-be4...

Re: Why we chose Vue.js

#215

Post by water42 »

thewhitetulip wrote: post #211
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…

I want to learn Angular2, but am struggling to find a good source, I want to also build real-time web UI, albeit not for visualization. The problem of documentation is very real. Thank you for the feedback on Vue! I will look at it now.

The Angular 2 documentation is actually really good IMO. Have you looked at the tutorial (https://angular.io/docs/ts/latest/tutorial/)?

Re: Why we chose Vue.js

#216

Post by catshirt »

vladimir-y wrote: post #141
iotscale wrote: post #123

Earlier quoted context omitted.

React is not a templater, it's a differ. The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code. Edit: After reading my comment again, I feel I must mention; even that similarity is not coming from React directly. It's JSX. Although they go like fish & chips together (Not a great analogy but I guess I'm hungry).

> React is not a templater, it's a differ. It's a templater, read my message above - an advanced tempalter, which means it has some DOM rendering optimizations. > The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code. Not just tags, but an entire "view" thing, a representation, so old fashion messy/sloppy/spaghetti-like PHP like code style.

nothing about React is messy or sloppy. it is the exact opposite.

the notion that your view logic and it's template must be completely decoupled is an antiquated and misguided best practice.

Re: Why we chose Vue.js

#217

Post by catshirt »

jakecodes wrote: post #190
49531 wrote: post #154

I actually interviewed with Jacob Schatz when he was trying to figure out which frontend framework to use for GitLab. I had been working in React for the last year or so which was apparent on my resume. He prefaced our interview with something to the effect of "I know you do a lot of React but we are not going to ever use React at GitLab" It was weird. I tried to ascertain his reasoning and pretty much all I got was…

Hi @49531. Sorry you felt that our conversation was weird. Regardless of my opinion of React, Vue or any Frontend Framework, I never want anyone to have a weird interview. My main feeling with Vue vs. React (maybe this should be a different post, as this post was meant to explain why Vue, and focus on the positives): 1. Vue is minimal to add in with existing code. React, is also not bad, but Vue is much simpler to mi…

1. i can't agree. it's possible to integrate React into your application one component at a time. how is Vue "much simpler to mix in"?

2. i think this depends on your background. if you've had the pleasures and displeasures of working through all the trials and errors of jQuery, then Backbone, then Ember, then Angular... React is painfully obvious to work with. because the problems it solves, the ways it solves them, and reasons for doing so are clear. if you're a new JS developer, maybe Vue probably has an easier learning curve. i'm also not sure why we are calling it a DSL when it's entirely plain JS. Vue templating- now that's a DSL.

3. valiant modus, but keep it contextual. simple can bite you in the ass. people don't introduce complexity for no reason (unless they don't know what they're doing, of course).

4. no... React is in fact just React. you can build a working UI without any supplemental React libraries. how is it "many other things" any more than Vue is?

Re: Why we chose Vue.js

#218

Post by iLemming »

linkmotif wrote: post #176
marpstar wrote: post #158

Earlier quoted context omitted.

Is there a name for this "feeling"? I feel this way about a lot of things that get "popular". I feel this way about React, in fact. React is "good" but I don't see it as our end-all be-all front-end savior. Vue.js is a lot more interesting to me because it's not popular...because it's the underdog. This Cracked article gave me a bit of consolation: http://www.cracked.com/blog/6-reasons-it-sucks-to-hate-popul...

Sure popularity ruins many things. Music, movies, books, software libraries. However, you don't have to use React. React is a set of concepts. I personally really enjoy programming with those concepts (I just wish it wasn't JS). If you don't want to use Facebook's implementation, there are many other implementations.

> I just wish it wasn't JS.

Try Clojurescript. It is truly amazing.

Re: Why we chose Vue.js

#219

Post by kamkha »

disease wrote: post #170
iotscale wrote: post #103

Earlier quoted context omitted.

I started reading through the docs and found it very similar to Knockout.js. Is here anyone who used both to tell the advantages of Vue? FYI, I'm thinking about dropping Knockout because some performance problems I'm having with a very specific use-case.

React with MobX, Vue and Knockout all seem very similar. I am wondering if TypeScript is a first class citizen in either MobX or Vue - in my experience seeing TypeScript everywhere in Angular 2 has been one of that platform's biggest wins.

MobX is written in TypeScript: https://github.com/mobxjs/mobx

Re: Why we chose Vue.js

#220

Post by SparkyMcUnicorn »

Svenskunganka wrote: post #129
WA wrote: post #127

I tried Vue.js a few months ago and liked it a lot. But now, I need to rewrite my apps and I decided to go the Cordova road with Ionic 2, because Ionic 2 is, imho, unparalleled in its quality. Ionic 2 uses Angular 2 and I wished there was some Ionic 2 + Vue.js bindings. However, after working with it for a bit, I found that Angular 2 is actually quite simple with the benefit of using TypeScript out of the box. Before…

Have you looked at Weex[1]? It's what Ionic is to Angular, the only difference is that Weex and Vue has an official collaboration and Weex has been embraced by Vue's developers - something that Ionic hasn't yet been by the Angular team as far as I'm aware. Note though that the collaboration is still very young between these two, but I believe we'll see some great things in 2017 from this collaboration! [1]: https://a…

Weex is in the process of becoming powered by Vue, but it's just "Vue inspired" right now. Evan talked about it in the Vue 2.0 announcement.

I would give it time before I use it.

Post reply on HN