Our long term plan to make GitLab as fast as possible with Vue and Webpack
1–10 of 304 posts
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#2Misleading title, from the article:
> We are not rewriting GitLab's frontend entirely in Vue.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#3[deleted]
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#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.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#5> 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.
Yet much easier to do by avoiding a single page app all together.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#6How about going forward by not focusing on using the latest JavaScript frontend, but fixing the backend issues you clearly have?
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#7> 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.
Yet much easier to do by avoiding a single page app all together.
[deleted]
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#8> 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.
Yet much easier to do by avoiding a single page app all together.
Is there anything meaningfully different between a site made up of a number of discrete single page apps and one built with Vue?
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#9How about going forward by not focusing on using the latest JavaScript frontend, but fixing the backend issues you clearly have?
Too soon? low blow? I would imagine they have different teams for the fronted and their backend datastore, and can do both at the same time.
Re: Our long term plan to make GitLab as fast as possible with Vue and Webpack
#10Can 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.