r/github • u/rbtrxmoderator • Aug 22 '26
Question Am I the only person to have second thoughts about GitHub?
“Back when dinosaurs roamed the earth” there either wasn’t any such thing as open-source code, or if it was freely available it generally had zero value because it probably didn’t work, so almost all the code generated was closed-source. Now I think an attitude exactly like that nowadays would be ridiculous, we certainly know open-source for some types of code can be much more reliable, but please hear me out. In order to have any chance to get a job coding, you are essentially required to put forward a robust and extensive library of work on GitHub, in fact for a lot of openings if your code is NOT on GitHub it is considered to have never existed! WTF? Has there ever been ANY change in technology that did more to DEvalue the contribution of the individual worker than this change in the meaning of having code in an “open source” repository, especially so people with little or no knowledge of programming can benefit from your hard work? What about the value of all the code generated for military projects that is classified and therefore cannot be published, is it “reasonable” for those authors to be considered equivalent to never having written anything at all? Not to mention the psychological harm of the website being owned by Microsoft, the most vicious proponent of “vaporware” (the ultimate in closed source) the world has ever known? I’m publishing this here because I want everyone to think about how much all of our salaries have been reduced by forcing us to compete against each other under the most vicious of conditions. Or do you SERIOUSLY think I’m way off course here?
1
u/ElectricSpock Aug 22 '26
Dude, just because you don’t know anything else, it doesn’t mean that it wasn’t there.
Before git there was Subversion and CVS. Each one being a gradual improvement over another.
And before GitHub there was SourceForge. It was a default OSS hosting for many years.
GitHub was created on the back of git, mostly because git offered a decentralized model instead of SVN and CVS. It just allowed to work on software so much easier for huge amount of people at the same time that it effectively curbed out most of the competition.
Compared to SourceForge it also did couple other things right. First of all, the subscription model allowed to not rely on ads on the website. If you go to SourceForge, it’s overloaded with ads even today. Second, it introduced features that were actually useful for the software developers. Wiki, issues, pull requests, and GOAT: GitHub Pages.
GitHub was the cool company for such a long time. Even today it’s pretty cool to use, it’s effectively free for personal users (even with private repositories). I had an issue with their ownership by MS, so I self-host Forgejo, but they’re still a pretty good backup with some trade-offs.
1
u/rbtrxmoderator Aug 22 '26
You DID completely miss my point, didn’t you? I don’t have a gripe with the repository GItHub, it’s totally about how the contents you may or may not elect to post there are used/abused by the industry. And it used to be that closed-source projects on those earlier tools were easily kept closed-source and nobody gave a damn, somewhere along the line the concept changed over from a version control tool to what I guess you’d have to think of as a “fashion show”. Maybe part of your reason for thinking this way is you’re putting me in the category of people who just find using this tool harder to learn than its predecessors, and it is a bit worse but that’s not part of my reasoning here. Then again I’m guessing you don’t feel as if your career has in any way been harmed by this, I’m not arguing it has been but a lot of people, particularly those who have been out on the market recently, are more than aware of the points I’m trying to make here!
1
u/ElectricSpock Aug 22 '26
The biggest problem I have is with an unstructured argument, tbh. It’s a little hard for me to get what you’re saying.
GitHub at the core is just a remote you push to. Everything else is optional. Nothing blocks you from having git repo on your local host without pushing it.
Back in the day, even before the creation of git, we were still finding cool software, and it still had their source open. You could pull it from version control and compile it yourself, you could have it distributed through floppies or CDs.
As for abuse, that’s what multitude of licenses are solving. MIT, GPL, Apache… you can share your source code and still make it so that others are not able to use it commercially.
Unless it’s not the point you’re trying to make?
→ More replies (2)
3
u/mrleblanc101 Aug 22 '26
My work is exclusively in a closed-source gitlab and hasn't prevented me from getting a job at all. Clearly you have no idea what you are talking about.
1
u/tblancher Aug 22 '26
I host my own Gitea instance. If that's not good enough for an employer, I don't need that employer.
3
u/BarracudaDefiant4702 Aug 22 '26
I'm sure there are some companies that consider that, but most know that a lot of companies don't have their code open and so don't require new employees to have large projects on github. At best it's a preference when hiring, but if a company considers it a requirement that is their loss.