Are you using Webpack directly with Rails? I'm curious how your development environment works.
Our long term plan to make GitLab as fast as possible with Vue and Webpack
51–60 of 304 posts
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#52Earlier quoted context omitted.
> 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.
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.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#53Earlier quoted context omitted.
> 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.
[deleted]
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#54I 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 state gets managed on the server to an extent. However, most apps are better as SPAs rather than these hybrids. Informational websites being the exception.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#55We 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!
> with SSLs as cheap as $4.99 per year
*As cheap as Free Ninety Nine
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#56Earlier 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?
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, nothing to run, just a JavaScript library that makes it easier to write view templates.
It would make it even easier to get into if that tutorial were written entirely in ES5, but you could use babel-standalone if you felt that JSX and ES6 were important enough.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#57I 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".
Performance matters - a lot. It's often overlooked because its effect on users is more unconscious than consciously noticed, but even small speedups greatly affect user motivation, as measured by any number of blog posts about "page load time" and "conversions".
However, "instantly smooth transitions" may not require using JavaScript. According to the blog post, GitLab observed a performance increase after ditching Turbolinks[1]. Indeed, sites that use JS to speed up page loads are often compensating for what would otherwise be an excessively slow load, due to having lots of scripts or whatnot. And that's only a partial fix: the user still experiences that slow load whenever they come in from an external site or open links in a new tab/window. If you can make "real" page loads fast, you avoid that problem.
[1] ...though it doesn't seem to have been measured very scientifically - to quote from the pull request: "I thought I noticed that pageloads were a lot more snappy, and one other reviewer said the same. Not the most rigorous way to test performance, but it helps."
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#58Earlier 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…
Thanks for replying! Our official tutorial was actually exactly that for _years_, but it didn't seem to help much. I get the sentiment though and maybe we can find another way to make it work.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#59I 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…
I've always been a pretty average front-end guy, but React actually makes me like writing front end code. It's just a great way to think.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#60Earlier quoted context omitted.
> 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.
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…
Both frameworks are the same with regards to compilation.
JSX can be used at runtime by including the babel browser compilation script. This is only recommended for development, not production. React can also just use plain javascript, although JSX is a much cleaner and easier to use with the rest of the framework.