Technoglitch
Core Member
Thursday, 21 January 2016
When it first appeared on the scene, Github was one of a kind and a true visionary amongst its rivals still using Subversion, Bazaar or Mercurial as their source control system.
Since then the scene has changed a lot, with many alternative options challenging the monopoly established by Github. However, its pre-eminent position allowed Github to more or less take for granted that every open source project out there would use it as its hosting service.
The problem is that Github hasn't been treating its free hosted open source projects and their contributors as real life customers who use it as a product. Of course, any software based product needs updates and upgrades but foremost a software provider has to listen to its clients' needs.
Github, relying on its number 1 spot, has neglected these needs to the point of sparking a pressing demand for action.
The cry for action was expressed in an open letter, signed by many top notch project maintainers, like Adam Bradley of Ioni; Dave Methvin of jQuery; Ryan Cavanaugh of TypeScript and more than 1,000 other devs.
In the letter now known as the "Dear Github" letter they collectively make the following statement :
"You have done so much to grow the open source community and make it really accessible to users. Somehow you have us chasing stars and filling up squares, improving the world’s software in the process.
However, many of us are frustrated. Those of us who run some of the most popular projects on GitHub feel completely ignored by you. We’ve gone through the only support channel that you have given us either to receive an empty response or even no response at all. We have no visibility into what has happened with our requests, or whether GitHub is working on them. Since our own work is usually done in the open and everyone has input into the process, it seems strange for us to be in the dark about one of our most important project dependencies."
This interest from GitLab has sparked lively conversations on the pluses and minuses of Gitlab vs Github as hosting services amongst the Github community, ironically appearing as an open Issue to the "Dear Github" project's page!
These discussions include suggestions such as :
"GitHub has a better UX and more features than GitLab. The advantage of GitLab is that you can freely install it on your own servers, hence a very cheap solution if you want unlimited private repositories for your team, compared to GitHub private repositories pricing."
and
"The big upside to GitLab is that it is all open-source"
and on the minus side
"Major con: The slowness is a major pain point for myself at the moment. I haven't hosted my own projects at GitLab so far, but just browsing other projects is quite terrible: every action takes seconds to complete. Every time you press anything you are looking at a 1-10 second wait. "
Of course GitLab aside, there are other contenders, each with its advantages and disadvantages. For example, Ubuntu's LaunchPad which recently started adding Git support into repositories making the switch from its Bazzar source control system.
Wikipedia also contains a "Comparison of source code hosting facilities" as Alternative.to does
Is it time to skim through that list?
Regardless of the answer to this question, one thing is certain: Github fell victim to its own success and with Pandora's box now open, anything is possible. Thinking the unthinkable, there is even the possibility, after so many years, of losing its hard earned crown to one of its competitors.
Github Victim Of Its Own Success
When it first appeared on the scene, Github was one of a kind and a true visionary amongst its rivals still using Subversion, Bazaar or Mercurial as their source control system.
Since then the scene has changed a lot, with many alternative options challenging the monopoly established by Github. However, its pre-eminent position allowed Github to more or less take for granted that every open source project out there would use it as its hosting service.
The problem is that Github hasn't been treating its free hosted open source projects and their contributors as real life customers who use it as a product. Of course, any software based product needs updates and upgrades but foremost a software provider has to listen to its clients' needs.
Github, relying on its number 1 spot, has neglected these needs to the point of sparking a pressing demand for action.
The cry for action was expressed in an open letter, signed by many top notch project maintainers, like Adam Bradley of Ioni; Dave Methvin of jQuery; Ryan Cavanaugh of TypeScript and more than 1,000 other devs.
In the letter now known as the "Dear Github" letter they collectively make the following statement :
"You have done so much to grow the open source community and make it really accessible to users. Somehow you have us chasing stars and filling up squares, improving the world’s software in the process.
However, many of us are frustrated. Those of us who run some of the most popular projects on GitHub feel completely ignored by you. We’ve gone through the only support channel that you have given us either to receive an empty response or even no response at all. We have no visibility into what has happened with our requests, or whether GitHub is working on them. Since our own work is usually done in the open and everyone has input into the process, it seems strange for us to be in the dark about one of our most important project dependencies."
This interest from GitLab has sparked lively conversations on the pluses and minuses of Gitlab vs Github as hosting services amongst the Github community, ironically appearing as an open Issue to the "Dear Github" project's page!
These discussions include suggestions such as :
"GitHub has a better UX and more features than GitLab. The advantage of GitLab is that you can freely install it on your own servers, hence a very cheap solution if you want unlimited private repositories for your team, compared to GitHub private repositories pricing."
and
"The big upside to GitLab is that it is all open-source"
and on the minus side
"Major con: The slowness is a major pain point for myself at the moment. I haven't hosted my own projects at GitLab so far, but just browsing other projects is quite terrible: every action takes seconds to complete. Every time you press anything you are looking at a 1-10 second wait. "
Of course GitLab aside, there are other contenders, each with its advantages and disadvantages. For example, Ubuntu's LaunchPad which recently started adding Git support into repositories making the switch from its Bazzar source control system.
Wikipedia also contains a "Comparison of source code hosting facilities" as Alternative.to does
Is it time to skim through that list?
Regardless of the answer to this question, one thing is certain: Github fell victim to its own success and with Pandora's box now open, anything is possible. Thinking the unthinkable, there is even the possibility, after so many years, of losing its hard earned crown to one of its competitors.
Github Victim Of Its Own Success
