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

Our long term plan to make GitLab as fast as possible with Vue and Webpack

about.gitlab.com

Post reply on HN
Print view View original

21–30 of 304 posts

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#21

Post by ng12 »

jordanlev wrote: post #16
dntrkv wrote: post #10

Can someone explain why someone would choose Vue over React (or one of the clones)? When I looked at the docs for Vue it reminded me of my Backbone days.

If you already know react and are happy using it, then there's no reason to use Vue. But if (like me) you were never quite able to figure out how to use React (especially all the build tooling that's suggested in every tutorial), then Vue is worth a look as it's incredibly simple to get started with and easier to learn. I find it especially appeals to people coming from a place of familiarity with html and css (where…

> easier to learn

I think this is problematic because people don't differentiate between React and the React ecosystem. Plain old React is just as easy (probably easier) than learning Vue. I always recommend the official React tutorial (https://facebook.github.io/react/tutorial/tutorial.html) before even thinking about Redux or Webpack or whatever.

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#22

Post by therealmarv »

dntrkv wrote: post #10

Can someone explain why someone would choose Vue over React (or one of the clones)? When I looked at the docs for Vue it reminded me of my Backbone days.

It's like the ideal mixture of React and Angular. You can use more the template approach than in React (where everything tends to be a component). Footprint (size of libs) is also smaller than React while still having VirtualDOM and speed of React. What I also experienced: It's much simpler to add Vue to existing HTML code without the need of bundlers and build tools like Webpack etc. Also keep in mind that Vue ecosystem is more from one hand: Vue itself, the store (Vuex), the router... all from one single source and team and not cluttered from various teams like in React ecosystem.

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#23

Post by [deleted] »

alexkavon wrote: post #20
camdenlock wrote: post #17

The escalating abuse of the word "awesome" is like the overuse of dynamic compression in music. When every expression is fever-pitched, there's little room for interesting expression. I also notice that the most shameless abuse of "awesome" seems to come from public-facing software developers, e.g. community managers and the like. It's become some kind of advertisement for a bland, safe, comfortable community where n…

Sounds awesome!

[deleted]

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#24

Post by therealmarv »

ng12 wrote: post #21
jordanlev wrote: post #16

Earlier quoted context omitted.

If you already know react and are happy using it, then there's no reason to use Vue. But if (like me) you were never quite able to figure out how to use React (especially all the build tooling that's suggested in every tutorial), then Vue is worth a look as it's incredibly simple to get started with and easier to learn. I find it especially appeals to people coming from a place of familiarity with html and css (where…

> easier to learn I think this is problematic because people don't differentiate between React and the React ecosystem. Plain old React is just as easy (probably easier) than learning Vue. I always recommend the official React tutorial ( https://facebook.github.io/react/tutorial/tutorial.html ) before even thinking about Redux or Webpack or whatever.

That's true. React itself is also clean and simple... but things tend to be more complicated in React, the ecosystem when you go to the SPA direction.

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#25

Post by jbigelow76 »

camdenlock wrote: post #17

The escalating abuse of the word "awesome" is like the overuse of dynamic compression in music. When every expression is fever-pitched, there's little room for interesting expression. I also notice that the most shameless abuse of "awesome" seems to come from public-facing software developers, e.g. community managers and the like. It's become some kind of advertisement for a bland, safe, comfortable community where n…

Make "radical" viable again?

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#26

Post by bcherny »

jakecodes wrote: post #13
dntrkv wrote: post #10

Can someone explain why someone would choose Vue over React (or one of the clones)? When I looked at the docs for Vue it reminded me of my Backbone days.

Backbone is a structural JS library/framework. It gives your app a backbone. Vue provides data binding so your View(Vue) gets automatically updated when data changes. Completely different.

Backbone implements 1-way binding via model:change event + render(). Vue/React/Angular do various forms of diffing, which makes their incremental rendering more efficient than Backbone's.

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#27

Post by elliotlarson »

dntrkv wrote: post #10

Can someone explain why someone would choose Vue over React (or one of the clones)? When I looked at the docs for Vue it reminded me of my Backbone days.

I'm mostly a backend Rails developer, but I've spent the last 3 months developing stuff with Vue, Elm, React, and Angular 2 in an effort to see which of the front-end frameworks I would like best (I messed with Ember a year ago but haven't had a chance to revisit since). To me it seems like React is about putting logic in code instead of templates/markup. Vue is more in the vein of Angular, where you have logic in your templates/markup. So it's sort of a question of what you feel more comfortable with, the style of Vue or the style of React.

Instead of Vue or React, you might choose Angular 2. Vue is sort of touted as "Angular done right". I did enjoy working with Vue (I actually enjoyed working with all of them), but I think Angular 2 may be "Angular done right". However, Vue seems to try to be more lightweight and less of a framework than Angular (1 or 2). It has this in common with React. I think both Vue and React would be easier to start introducing into an existing app incrementally. Angular 2 seems like it's more of a framework/holistic choice. It has this in common with Ember, although this is true of Ember to an even larger degree.

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#28

Post by crispinb »

camdenlock wrote: post #17

The escalating abuse of the word "awesome" is like the overuse of dynamic compression in music. When every expression is fever-pitched, there's little room for interesting expression. I also notice that the most shameless abuse of "awesome" seems to come from public-facing software developers, e.g. community managers and the like. It's become some kind of advertisement for a bland, safe, comfortable community where n…

"Awesome" rocks.

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#29

Post by bcherny »

calcsam wrote: post #19

There's an entire cottage industry of 3 to 5-year old series Bish startups porting Backbone // jQuery apps over to more modern frameworks. We are moving ours over to React at Plangrid (mostly done), Gusto is mostly done with their migration as well. Would be interesting to figure out how many startups are in this category.

Angular 1 + CoffeeScript -> React + TypeScript here. Mostly positive experience, though taking sigificantly longer than we planned.

Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack

#30

Post by toomuchtodo »

jbigelow76 wrote: post #25
camdenlock wrote: post #17

The escalating abuse of the word "awesome" is like the overuse of dynamic compression in music. When every expression is fever-pitched, there's little room for interesting expression. I also notice that the most shameless abuse of "awesome" seems to come from public-facing software developers, e.g. community managers and the like. It's become some kind of advertisement for a bland, safe, comfortable community where n…

Make "radical" viable again?

Bodacious.
Post reply on HN