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

How we do Vue at GitLab: one year later

about.gitlab.com

Post reply on HN
Print view View original

141–150 of 208 posts

Re: How we do Vue at GitLab: one year later

#141

Post by Rusky »

nightski wrote: post #136
Rusky wrote: post #91

Earlier quoted context omitted.

As far as the actual libraries themselves go, if any of Vue/Angular/React are the new jQuery, it's Vue. It's the smallest of the three, but more importantly it's the easiest of the three to drop into a page without any tooling.

I have a hard time understanding why this "drop in" experience is so important. Are you all writing simple contact us forms or something incredibly simple? Any application that I've built which actually required a technology like Vue or React was a significant undertaking and a few hours getting up and going (not that either of them require anywhere close to that) is nothing.

I don't see how jQuery could have been anywhere near as ubiquitous if it had required a build step.

It makes experimenting easier for beginners, for people considering switching to it, for people who are already using it and want to try something outside the context of their existing codebase, for people writing tutorials and demos, etc.

The less bullshit to wade through when using a tool, the more situations it will be applicable to, regardless of skill level or project size.

Re: How we do Vue at GitLab: one year later

#142

Post by luord »

sametmax wrote: post #83
giantsloth wrote: post #79

Earlier quoted context omitted.

I implore you to checkout create-react-app to get a hello world really quick: https://github.com/facebookincubator/create-react-app npm install -g create-react-app create-react-app my-app cd my-app/ npm start Your sentiment is correct that tooling around these pieces of technology needs to always be first class. React failed miserably, and Vue did an AMAZING job. I'm probably starting to sound like a shill for React.…

I used that. I took me a huge time just to understand what all the tooling was doing, how to integrate it in my current stack and how it was going to affect my current project. My pet peeve with react is that I can't just code. I have to stop every 10 steps and reflect on the tool I use, instead of the problem I'm trying to solve.

> My pet peeve with react is that I can't just code. I have to stop every 10 steps and reflect on the tool I use, instead of the problem I'm trying to solve.

Thank you! Every time I've tried react (and enough attempts were made to finally decide it was just not for me), there was always something in the back of my mind that I didn't like and I just couldn't put it to words. You just described what it was.

And, if one forgoes tooling, then the situation is like the one you described in your previous comment: an afternoon just to get a "Hello world".

Re: How we do Vue at GitLab: one year later

#143

Post by [deleted] »

computerex wrote: post #103
sametmax wrote: post #83

Earlier quoted context omitted.

I used that. I took me a huge time just to understand what all the tooling was doing, how to integrate it in my current stack and how it was going to affect my current project. My pet peeve with react is that I can't just code. I have to stop every 10 steps and reflect on the tool I use, instead of the problem I'm trying to solve.

I have no idea what you are talking about. React doesn't require any tooling. Drop a reference to React from some cdn in your HTML file and you are good to go. People confuse the myriad of libraries and tools complementary to React for React. You don't need create react app for Hello world. Create React App gives you a zero configuration way to not only write hello world, but also bootstrap a non-trivial production r…

[deleted]

Re: How we do Vue at GitLab: one year later

#144

Post by lightblade »

gt5050 wrote: post #30

At my last job we did a comparison between Vue and React before rewriting a major frontend application. We did a POC in both React/Vue and ended up using Vue mainly due to the following reasons: Single File Components Single file components (.vue files) is the best thing about Vue. I understand this might be a personal preference, but we wanted to avoid CSS-IN-JS. Our designer could churn out neat html/css, but was a…

> Standard / Official way of doing things

If you like that, why not go with Ember?

Re: How we do Vue at GitLab: one year later

#145

Post by philliphaydon »

k__ wrote: post #12
ng12 wrote: post #3

> We discovered that VueX makes our lives easier. If you are writing a medium to large feature, use VueX. If it's a tiny feature, you might get away without it. I feel like this is Vue starting to get the React treatment. React was (and still is!) a very simple library until people realized they needed to do fancy things to make complex applications manageable. Redux came out, everyone fell in love with it, and React…

Funny thing is, Vue wihtout extras is more complex than React without extras.

I disagree. I was going to use react for a personal project and got stuck because of documentation and the various blog posts and tutorials all being different and using different libraries and patterns etc etc. This made getting a basic hello world impossible for me. (I’ve since used react and it’s now trivial but starting out was not easy, barrier to entry is still higher than vue.)

Vue on the other hand was so simple. And the documentation made getting hello world done in a few minutes. This got me off the ground and made me feel productive as I felt I knew right away what vue was doing at a most basic level. Then it was just constant learning on top.

Re: How we do Vue at GitLab: one year later

#146

Post by philliphaydon »

saas_co_de wrote: post #123
lucisferre wrote: post #49

I would strongly disagree that it is ok to use jQuery with Vue. I mean sure, it's ok in that most of the time it isn't going to hurt or break anything, at least if you are just using it to query elements from the DOM. However, I would argue that is not ok in that it should never be necessary and it's use would be a code smell to me and indicate that the code in question is likely not using Vue properly. I suspect it…

> However, after doing the research, we found that it is not a good idea to use jQuery with Vue I have a hard time taking seriously the opinion of someone who bases their sweeping global assertions on "research" and not on actual experience.

The only time I needed jquery was when I was using bootstrap, and that was easily solved by ditching bootstrap and going with bluma.

Re: How we do Vue at GitLab: one year later

#147

Post by nikcub »

saas_co_de wrote: post #125
juddlyon wrote: post #35

React made me feel stupid, Vue made me feel smart. So I use Vue. I came at it as a long-time jQuery dev with Angular 1 experience.

React made me feel that the designers of react are stupid - so kind of a similar experience :)

Whats with the insults? I can get preferring one platform over another, but insulting people is just lame.

The React and Redux developers are incredibly good at what they do - they've also spent a lot of time putting out material, books, video courses, blog posts, talks help everybody else understand the new paradigm they've created

They can't be that stupid when a lot of modern javascript framework components are either direct clones of, or influenced by, their work

Re: How we do Vue at GitLab: one year later

#148

Post by lenkite »

gt5050 wrote: post #30

At my last job we did a comparison between Vue and React before rewriting a major frontend application. We did a POC in both React/Vue and ended up using Vue mainly due to the following reasons: Single File Components Single file components (.vue files) is the best thing about Vue. I understand this might be a personal preference, but we wanted to avoid CSS-IN-JS. Our designer could churn out neat html/css, but was a…

Well, this approach of single file components (.vue) containing separately scoped HTML, CSS and JS is what the Google Polymer team were recommending all the way for the last several years, but it seems no one was listening to them.

Re: How we do Vue at GitLab: one year later

#149

Post by nightski »

sametmax wrote: post #140
nightski wrote: post #137

Earlier quoted context omitted.

Uh, you pass data & callbacks through props in vue also, unless you use a single component. Why not just compare it to using a single component in react then also and be honest?

Actually beginers in view won't use a component at all. They will use it angulajs 1 style

That's my point. You don't have to in react either.

Re: How we do Vue at GitLab: one year later

#150

Post by nightski »

Rusky wrote: post #141
nightski wrote: post #136

Earlier quoted context omitted.

I have a hard time understanding why this "drop in" experience is so important. Are you all writing simple contact us forms or something incredibly simple? Any application that I've built which actually required a technology like Vue or React was a significant undertaking and a few hours getting up and going (not that either of them require anywhere close to that) is nothing.

I don't see how jQuery could have been anywhere near as ubiquitous if it had required a build step. It makes experimenting easier for beginners, for people considering switching to it, for people who are already using it and want to try something outside the context of their existing codebase, for people writing tutorials and demos, etc. The less bullshit to wade through when using a tool, the more situations it will…

That's just it though, Vue & React aren't for most web sites. There is no point in pulling either in unless you are building something much more complex than where jQuery would suffice. There is no need for a technology to be "ubiquitous", just that it is going to meet the demands your application has for it.
Post reply on HN