Live data from Hacker News

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

about.gitlab.com

61–70 of 304 posts

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

#61
post #39

Earlier quoted context omitted.

Of course it's subjective, and different people coming from different backgrounds / experience levels find different things easier than others. But... that tutorial you say you like to show people utilizes jsx, which needs to be compiled with something (right? Or does react do the compilation automatically at runtime now and I missed that memo?). And for people coming from a place where they are very comfortable and…

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?

To get started with Vue, all you need is to include 1 javascript file, and it works with plain old javascript, all the way back to IE9. As one gets more advanced, there is the ability to compile templates, but that is an optional thing that no beginner needs to worry themselves about.

I took a closer look at your tutorial. It's really very good! And I like that you link to a codepen which gets people up and running without having to even create their own html file.

Tutorials speak differently to different audiences -- I imagine people used to building more traditional "apps" get a lot out of this one.

But speaking from the perspective of someone who spent years making html+css pages that had data piped into them from the back-end (PHP, Rails, etc)... the scope of the tutorial is somewhat overwhelming to me :) It goes right into components, shared state, immutability, functional programming, history... to some people that is a lot of concepts at once. I think the appeal of Vue (to a certain slice of people) is that you can just add it as a "light touch" onto an existing html page. For example, show me one textbox who's value gets displayed in a div somewhere else on the page as I type, or one button that toggles the visibility of one image. Just super duper basic stuff, in very isolated and limited-scope chunks, and in the context of "easy dom manipulation" (as opposed to "building a game or app").

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

#62
post #54

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…

IMO this is not true at all. Any non-trivial SPA not based on a framework will end up inventing one eventually that solves the very same problems which were already solved for you. Examples being history management and back button, state management (especially if you prefer immutability), and server side rendering. On the other hand, if the app is not an SPA, you probably don't need the framework. Both history and st…

Maybe by Vue they mean Vue + vuex + Vue router.

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

#64
It's good to see vue.js getting some love. I believe it would be the preferred Web framework these days if it had backing from FB like React does. Too many people fall into the trap of believing a tech is the best just because some big Corp sponsors it. I fell for Angular once for the same reason.

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

#65
post #54

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…

IMO this is not true at all. Any non-trivial SPA not based on a framework will end up inventing one eventually that solves the very same problems which were already solved for you. Examples being history management and back button, state management (especially if you prefer immutability), and server side rendering. On the other hand, if the app is not an SPA, you probably don't need the framework. Both history and st…

I agree with this. If you're augmenting a traditional request/html-response web app with some JavaScript functionality, a lighter weight view library fits the bill nicely. But, if you're developing a SPA that consumes an API, you might really enjoy what a more holistic framework provides in terms of code structure, front-end data management, and just general guidance on how to do certain standard things, like basic CRUD.

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

#66

It's good to see vue.js getting some love. I believe it would be the preferred Web framework these days if it had backing from FB like React does. Too many people fall into the trap of believing a tech is the best just because some big Corp sponsors it. I fell for Angular once for the same reason.

disagree. React has amazing reasons why it is fundamentally better than most of the other libraries for projects at scale.

I think vue is a perfect fit for gitlab but not quite perfect for facebook or a more complex web app on the front end.

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

#67
post #66

It's good to see vue.js getting some love. I believe it would be the preferred Web framework these days if it had backing from FB like React does. Too many people fall into the trap of believing a tech is the best just because some big Corp sponsors it. I fell for Angular once for the same reason.

disagree. React has amazing reasons why it is fundamentally better than most of the other libraries for projects at scale. I think vue is a perfect fit for gitlab but not quite perfect for facebook or a more complex web app on the front end.

what reasons?

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

#68

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!

HubSpot charges $100 per month. The SSL "option" is really close to robbery when companies charge so much.

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

#69
post #52

Earlier quoted context omitted.

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.

I sorta hate that React is so simple and the ecosystem is such a clusterf*ck. I wish they came out with a storage/persistence system as simple conceptually as the renderer. Maybe that's a lot to ask for though. React by itself gives me blue balls.

I have a theory that every project eventually approaches a level of complexity reflecting the level at which a moderately intelligent person can't understand it any more. I think of it as a "complexity budget". So if you start with something simple (say, React) then people will just invent more layers of complexity around it to solve whatever the next layer of problems is (Redux, Webpack, etc). And they won't stop until the complexity budget is all used up.
Post reply on HN