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

281–290 of 304 posts

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

#281

Post by chiefalchemist »

mi100hael wrote: post #274
paulddraper wrote: post #254

Earlier quoted context omitted.

> Generate the markup on the server and send it down to the client! It's post-modern web development. Agreed, but currently there is no great solution that allows you to do that and provide the kind of UI dynamism that really does improve UX. There are solutions that use the same templating server and client side, but they are far from pedestrian.

> Agreed, but currently there is no great solution that allows you to do that and provide the kind of UI dynamism that really does improve UX. Strongly disagree that there's any actual improvement on UX. Plenty of sites like GitLab, GitHub, YouTube, etc. insist on using JS to load what could be entirely separate pages, but instead leave the user with some slow, hand-rolled progress bar on the top of the page. For sit…

Furthermore, and pardon me if this is stating the obvious, but improving the underlying technology for UX does not necessarily lead to an actual improved UX. Look around. There continues to plenty of misused (?) technology (i.e., crappy user experiences.)

In short, technology isn't the problem with most UXs.

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

#282

Post by chiefalchemist »

fleshweasel wrote: post #88

One of the biggest reasons I favor React is that it's much easier to add a templating language to a programming language (i.e. JSX) than the other way around. Every construct for making decisions based on your data, traversing your data, etc. is more cumbersome and harder to validate in handlebars or whatever identical looking templating language the community came up with this week. I also am strongly against string…

Why would you? React is a tool. The fact that FB doesn't use the tool correctly shouldn't reflect negatively on the tool. That "honor" goes to the product.

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

#283

Post by wikyd »

__luke wrote: post #115
wikyd wrote: post #51

Are you using Webpack directly with Rails? I'm curious how your development environment works.

Yep! webpack-rails gem https://github.com/mipearson/webpack-rails

Awesome, thanks! We're using this too, but have been thinking about making the switch to https://github.com/rails/webpacker

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

#284

Post by lostsock »

tomstuart wrote: post #56
spicyj wrote: post #39

Earlier quoted context omitted.

create-react-app is our recommended way to build simple React apps (and some complex ones). It has no configuration and is designed to be very easy to set up. (My understanding is that Vue templates also need to be compiled -- is that incorrect?) I wrote the tutorial. Could you give any suggestions on how I could make it easier to get into?

Not the OP, but I'll state the obvious on their behalf. The number one thing that you (and Facebook) could do to help people learn React, and combat the perception that it requires overly complex tooling, is write a tutorial that shows how to use React entirely in-browser without any build toolchain. A static HTML file, some tags pointing at a CDN — done. No distractions, nothing to download, nothing to install, noth…

I think this post is spot on. I remember having a quick exploratory play with React back when the tutorial was like that and I thought it was great. Then when I came back to actually use React in a project the tutorial had changed and all of the sudden it felt like a big learning curve. Vue had just been adopted by Laravel and I was able to get everything I wanted to do by just including some scripts.

I've since learned more about compiling and including other resources so could probably handle the React tooling and requirements now but back when I started it was a big stumbling block.

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

#285

Post by jayajay »

philliphaydon wrote: post #280
jayajay wrote: post #248

Earlier quoted context omitted.

> I hate writing react. Out of curiosity, what was the straw that broke the camel's back?

After a few hours of Vue / Riot I could sit and begin writing a full fledged app. React for me was a bigger barrier to entry, i kept running into road blocks and searching google how to do things then everything is like "you need flux" or all these other things and I just got more confused and frustrated. Once you know it, its great, powerful, fast, a pleasure to use. But I still prefer vue/riot. Simple easy straight…

Thanks for sharing. Enough people are hopping onto the React → Vue train for it to be worth looking into.

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

#286

Post by mullsork »

keymone wrote: post #214
duncanawoods wrote: post #116

Earlier quoted context omitted.

JSX frustrates me. When did we suddenly start thinking syntax was desirable again? When did the complexity of combining markup syntax and a programming language become a good idea? Why are we forcing this crazy complexity into every language and every IDE / code editor out there? I much prefer react with standard functions e.g. var element = DOM.p({id : "thing"}, DOM.div(), DOM.div()); You can use an API like this in…

having played with clojure i really fell in love with hiccup syntax: var element = hiccup [p {id: "thing"} [div "first"] [div "second"]] https://github.com/lantiga/react.hiccup

Yeah hiccup syntax is my favorite as well. JSX is mentally the same thing for me except I read "HTML" faster than data structures if that makes sense.

I wonder if Hiccup was the first one to introduce this syntax? I never bothered to check but I always thought the JSX inventors might have been inspired by it.

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

#288

Post by richardwhiuk »

jazoom wrote: post #70
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?

Different teams dude

Same company, you just have to choose where to spend your resource, and from the analysis it looks like the operations and management side isn't where GitLab chooses to spend it's money.

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

#289

Post by richardwhiuk »

audleman wrote: post #43
jakecodes wrote: post #12

Earlier quoted context omitted.

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.

Well that's kind.

I wasn't trolling - I'm serious. If you are operations are in this bad a state, is investing a bunch of money in changing JavaScript frameworks on the frontend really the best use of your capital resource.

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

#290

Post by jazoom »

richardwhiuk wrote: post #288
jazoom wrote: post #70

Earlier quoted context omitted.

Different teams dude

Same company, you just have to choose where to spend your resource, and from the analysis it looks like the operations and management side isn't where GitLab chooses to spend it's money.

So you think they should pull their front-end dev team to do operations instead? I doubt that would go down so well.
Post reply on HN