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

151–160 of 208 posts

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

#151

Post by nightski »

sametmax wrote: post #138
nightski wrote: post #135

Earlier quoted context omitted.

Which order did you attempt to learn them in? Is it possible taking the time to attempt to learn react affected how easy it was to pick up Vue? I know we love to hate on React here but they are very similar. Can you identify what in particular is so confusing with regards to react vs. vue? They have a very similar API.

Vue dlc is better. Vue doesn't require webpack. All vue tutorials agree on how to so things and they work the first time you try them. You son't have to learn a new way to do templates or pass data. You can start withou components. You can even start without npm. In summary, vue offers a simpler hands on experience while allowing smooth learning curve to more complicated setup matching react's. React just throws you…

Vue requires webpack when going for anything beyond a simple hello world experience. At some point beginners are going to have to enter the real world.

BTW - You don't need webpack for React either. It is entirely possible to write React without it.

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

#152

Post by [deleted] »

computerex wrote: post #105
sametmax wrote: post #63

Earlier quoted context omitted.

Nope. Nope. Nope. Trainer here. I train in React and in Vue. My students do 3 times the work with raw vue than in raw react. Every one of them. All the time. It's not even on the same map.

Also a trainer and my students do 6x the amount of work in raw react than with vue. Every one of them, all the time. Looks like Vue sux. EDIT: In case this wasn't clear to you, I made this comment to highlight how ridiculous you sound. I don't know about you, but I don't select my tools based on how easy it is for students to learn them. I am a professional software engineer. Tool selection is driven by requirements.…

[deleted]

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

#153

Post by nikcub »

snarkyturtle wrote: post #133
giantsloth wrote: post #42

Earlier quoted context omitted.

I agree that single file components are awesome. I wish you had been introduced to styled components in react: import styled from 'styled-components' const Container = styled.div` padding: 10px; background: ${ ({ isHovered }) => isHovered ? 'green' : 'red' }; ` const H1 = styled.h1` font-size: 15px; ` const P = styled.p` font-size: 10px; ` const MyComponent = ({ isHovered }) => { return ( Hello This is a thing ) }

There is the Vue equivalent though: https://github.com/styled-components/vue-styled-components

Why do packages like this need to be ported or re-implemented for Vue rather than referenced? That package hasn't been updated since August while the root styled-components library has ~700 closed issues and 11,300 watchers

I've seen it with other stacks as well with almost complete re-implementations, a lot of duplicated effort and it feels like it goes against the packaging philosophy for javascript

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

#155

Post by [deleted] »

nightski wrote: post #40
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.

In general it's best to push your comfort boundaries. It's called learning. I'm not saying React is better than Vue (I honestly think they are very similar). Just that picking a technology based on whether it challenges you or not is probably not the best strategy.

[deleted]

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

#157

Post by agentPrefect »

So I've used Vue for personal projects before, it's really nice. I lead the dev on a small team within a large corporate company, we focus on React & Angular(io).

The primary reason why I would not adopt Vue is because Vue is still driven by Evan You - which is great, but if something had to happen to the guy (and I hope nothing does), I'm unsure Vue would have the long term support & drive it does right now.

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

#158

Post by Karupan »

I personally have been bitten by the two way binding and CSS in JS "feature" more than once. As an angular developer for two years, it frustrated me to no end.

React took time to learn, but it was definitely worth it. The one way data flow and explicit event handling (aka no ng- or v- tags) just seems cleaner to me.

Of course this is no way a critique of Vue. Its a great framework for people who want that sort of thing.

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

#159

Post by kuschku »

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…

The point is about not using external builds of react, but trying to understand what every piece does.

That means you want to be able to understand it well enough to write the webpack required for a react pack from memory.

And with react, that's years of learning.

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

#160

Post by cc81 »

jorblumesea wrote: post #88
savanaly wrote: post #86

Earlier quoted context omitted.

What was it about React that made you feel stupid? I can see how Redux would make someone feel that way but react is so simple I'm having a hard time visualizing someone not liking it for that reason.

Imo, doing it the "right way" and scalable requires a fair amount of knowledge about React before you pick it up. Things like ducks structure, redux thunks, store vs local state and other advanced usages. While not strictly necessary, it becomes increasingly important when building a large application. And then each of these are not official plugins so there's lots of differing opinions on how these pieces fit togeth…

But that is Redux and not React way. I bet for example Facebook themselves does not follow "the right way".
Post reply on HN