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

41–50 of 304 posts

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

#41

Post by spankalee »

chiliap2 wrote: post #4

> For example, the profile page could be potentially very light, and there would be no reason for that if someone is linked directly to the profile page; it should load every single piece of Javascript in our project. There are plenty of ways to do that with single Page apps; it's not a great argument against all single page apps, just poorly designed ones.

Exactly.

The Polymer CLI by default builds SPAs that only loads the resources needed for each page. It doesn't require a very complex toolchain or advanced knowledge.

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

#42

Post by flukus »

chiliap2 wrote: post #4

> For example, the profile page could be potentially very light, and there would be no reason for that if someone is linked directly to the profile page; it should load every single piece of Javascript in our project. There are plenty of ways to do that with single Page apps; it's not a great argument against all single page apps, just poorly designed ones.

An SPA has to be an "all in" thing though. If visiting the profile page then going back to the rest of the app is a possibility then the page load time is too high. SPA load times are only accepted because they are a one time cost.

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

#43

Post by audleman »

jakecodes wrote: post #12
richardwhiuk wrote: post #6

How about going forward by not focusing on using the latest JavaScript frontend, but fixing the backend issues you clearly have?

Thanks! We are working on the backend and the frontend at the same time. We have two separate teams.

Saying thanks to the troll... I admire your tact but just want comments like his to die a silent death.

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

#44

Post by msoad »

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.

React has no templates which is an advantage until it hits you with large bundle sizes. Every line of JSX is transformed into a longer JavaScript program.

I love that React makes developers more productive with JSX but there should be a way of outputting HTML for large template like React components. Browser are much happier dealing with HTML.

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

#45

Post by developer2 »

jorblumesea wrote: post #38

I really think for most cases you only need a view library instead of a heavy application framework. There are only a few cases there something as heavy as Angular or Ember is justified and in many scenarios a thinner view layer like Vue, React, Inferno etc is much better suited. Most of the web is simple enough to not need fancy http features or complex routing support. Everyone rushed to Angular without considering…

Unfortunately for GitLab, they've locked themselves into a position of trying to compete directly with GitHub. If GitHub has instantly smooth transitions between page loads while browsing a repository, then GitLab is going to follow suit. It's really hard to be competitive while ignoring the nagging thought that "competing requires copying the competitor".

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

#46

Post by StavrosK »

Jarwain wrote: post #36
elliotlarson wrote: post #27

Earlier quoted context omitted.

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

What are your thoughts on Elm compared to the other three?

Isn't elm a language? Why compare it with frameworks?

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

#47

Post by elliotlarson »

Jarwain wrote: post #36
elliotlarson wrote: post #27

Earlier quoted context omitted.

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

What are your thoughts on Elm compared to the other three?

I was really excited about Elm after listening to The Changelog episode #218 (https://changelog.com/podcast/218). Elm is in the style of React, but the flavor of Haskell. For my part, I had a hard time with the syntax and functional approach of it from the get-go. It was very new and awkward to me, which was a speed bump to my adoption. However, I felt like it held the promise of allowing potentially better/ more maintainable code. Evan Czaplicki (the creator) and Richard Feldman (a prominent evangelist) both talk about how the Elm language and style led to more effortless refactorings in larger front-end codebases they were working on. Sounded really good to me! But, I eventually ended up leaving my Elm journey and starting my Vue journey because the Vue documentation was so good (comparatively) and the style of Vue felt more natural to me. It kind of came down to the question "how do I do CRUD with this?". For me, the story was easier and more fleshed out with Vue. Currently, I'm working with Angular 2 mostly because it had a more definite answer to this question than Vue. And, the testing situation seemed way more fleshed out than Vue's (at least at this point). But, I plan to check back in on both Vue and Elm in the next year or so to see where they've landed. I understand what people are saying about JavaScript fatigue, but there's also so much exciting and cool stuff happening in this space right now. It's hard not to love all this innovation.

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

#48

Post by elliotlarson »

StavrosK wrote: post #46
Jarwain wrote: post #36

Earlier quoted context omitted.

What are your thoughts on Elm compared to the other three?

Isn't elm a language? Why compare it with frameworks?

So, I'm still a noob with this stuff, but it's my take that Elm is both a language and a front-end framework. It's a language that compiles down to JavaScript that also gives you a React-like toolset to develop front-end code with.

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

#49

Post by rkunnamp »

We at http://www.reportdash.com uses Backbone + Backbone Layout Manager + Jade

Every time I see a post like this , I feel sad for being less cool. I try to learn a bit of the mentioned cool framework. Then I realise, how awesome my current set up is.

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

#50

Post by joering2 »

rkunnamp wrote: post #49

We at http://www.reportdash.com uses Backbone + Backbone Layout Manager + Jade Every time I see a post like this , I feel sad for being less cool. I try to learn a bit of the mentioned cool framework. Then I realise, how awesome my current set up is.

> Add On: Custom Domain with SSL - $50 per month

Great way to discourage companies from handling their data online in a secure way.

Seriously with SSLs as cheap as $4.99 per year, your pricing feels like its 1999 all over again!

Post reply on HN