News for hackers. Stuff that matters.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by lolinder on Tuesday May 02, 2023 @10:08AM (#35787632)
While I do worry about github, I disagree that the dominance of git is a problem. At some point every industry grows up and standardizes on something, anything, because any standard is better than no standard.

Git is far from an ideal solution, but it has emerged as the standard way to manage version control in a software project, and we benefit from there being a standard. Version control is the first barrier to entry in starting on a new project, so having an industry standard for version control benefits everyone: open source projects get more contributors, companies don't have to train new hires on their system, and employees have one fewer barrier blocking them from specific jobs.

Could we have standardized on a better system? Certainly. But launching a competing standard at this point isn't going to make things better, the best case scenario is that it fragments the industry.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by gspencley on Tuesday May 02, 2023 @10:22AM (#35787882)
Git is also FOSS and is not owned by Microsoft / Github. Using git doesn't really "give" Github anything other than a bit of convenience and brand linkage. If the industry wanted to adopt a git replacement I suppose that Github's use of git could be a hinderance, but honestly the coupling is pretty loose.

Also, I worked in consulting for a few years and while Github was common, so was Azure devops (ironically also Microsoft, though) and one project used BitKeeper. Github might be dominant, but is very far from a "monopoly" in my opinion (I don't know if anyone used that word but if that's not the concern then what's the big deal?)

Re:Let's Make Sure GitHub Doesn't Become the Only Option by JohnFen on Tuesday May 02, 2023 @10:48AM (#35788322)
Yes, my experience is that Github isn't actually universal. I've yet to work for a company that uses it, personally. My only interaction with Github is in the hobbyist realm when I want code from an OSS project that is hosted there.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by bguebert on Tuesday May 02, 2023 @11:09AM (#35788688)
This has been my experience too. I think of Github as more like a social media platform that incorporates git as a convenient feature. Large corps use it as a marketing/PR forum and regular people use it to connect to other people interested in programming.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by jfreax on Tuesday May 02, 2023 @12:47PM (#35790415)
But what software are large corps use then? I work at a fairly large coorp (>650000 employees) and they are indeed using Github Enterprise (and some other solutions like Bitbucket data center). I'm would be quite surprised if they really only use software like Github for public things.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by nanidin on Tuesday May 02, 2023 @01:15PM (#35790923)
I worked at a company circa 2010 with around 2000 engineers that used git + gerrit + Jenkins + JIRA.

Worked at another company circa 2015 with around 80k employees (not sure how many engineers) that used git + cgit + Jenkins + JIRA.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by JohnFen on Tuesday May 02, 2023 @12:56PM (#35790601)
With my last four employers, two used subversion, one used git (just git -- not github or the like) and my current one uses whatever Azure Devops is using.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by shotnothing on Tuesday May 02, 2023 @01:09PM (#35790828)
gitlab is what my company uses
Re:Let's Make Sure GitHub Doesn't Become the Only Option by WorldMaker on Tuesday May 02, 2023 @04:19PM (#35793550)
Azure DevOps is in a weird zombie state where everyone knows Github is getting all the development attention (and presumably most of the workforce now) but Microsoft is keeping it on just enough life support to keep companies "happy enough" and are still refusing to call it "dead". (They continue to point to the development roadmap, which is still actively maintained, but to some like me read very much like "bare minimum maintenance feature set". It also doesn't help that of the few open repositories for checking in on AzDO development, such as their community proposals repo, which are themselves hosted on Github, hah, it is very transparent most haven't seen active commits since 2019 or 2020.)

Bitbucket has a lot of Jira-integration and a lot of large corps are in Jira for the long haul now and "might as well get the synergy of Bitbucket".

Plus, don't underestimate the sunk cost fallacy factor keeping a lot of large corporations locked into things like Perforce and ClearCase.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by jruohonen on Tuesday May 02, 2023 @02:06PM (#35791756)
Exactly this: I hate that GitHub is indeed very much like a social media. Expect also all the weird algorithmic surveillance to work underneath.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by toastal on Wednesday May 03, 2023 @03:16AM (#35799134)
Self plug: https://sr.ht/~toastal/github-less-social/

I made a filter list for uBlock Origin (and compatible) ad-blockers that can hide many of the social media aspects of Microsoft GitHub to make it a bit more tolerable when forced to interact with it due to project lock-in.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by npteljes on Tuesday May 02, 2023 @06:22PM (#35795015)
I have seen it used on a commercial project, but I couldn't fathom why they were doing it. I guess business people did their thing. Large healthcare related project in the US.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by rob74 on Tuesday May 02, 2023 @11:02AM (#35788551)
TBF the argument that some people use GitHub because it offers a more pleasant experience than using git itself (via the CLI) might have some truth to it. But saying "GitHub is what most people use because it makes the complexities of git easier" goes a bit too far. Local git GUIs like Sublime Merge are better for that - GitHub might help you with the complexities of collaborating with others using git, but it won't save your ass if you've got your local repo in some wonky state...
Re:Let's Make Sure GitHub Doesn't Become the Only Option by JonChesterfield on Tuesday May 02, 2023 @11:15AM (#35788806)
An anecdote, but it's really difficult to search for information on git. Pretty much everything I find is specific to GitHub. Though that might be a problem with me still using Google to try to find information.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by gspencley on Tuesday May 02, 2023 @11:37AM (#35789237)
Yeah I switched to DuckDuckGo a long time ago and now I might switch to Brave Search because its "Goggles" feature is pretty cool (basically lets you rerank search results according to preference, ex: give precedence to tech blogs, or URLs popular in HN comments, down-rank most popular sites etc.).

This is getting off-topic, but at a certain point Google's results started to feel less and less relevant. Strict keyword matching stopped becoming a feature since it started to "guess" the "hidden meaning" behind your searches, modifiers like "include this exact text" and -"exclude this" stopped being supported and the amount of crap it throws in the search results that are not links to websites became distracting and annoying much of the time rather than useful.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by toastal on Wednesday May 03, 2023 @03:26AM (#35799196)
Related to search though, Microsoft GitHub does not allow you to search the source code of projects with the search bar unless you are authenticated.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by alwaysbeconsing on Tuesday May 02, 2023 @12:03PM (#35789674)
I would suggest bookmarking this: https://git-scm.com/book/en/v2 I have found the how and why of pretty much everything I've ever needed to do with git there. You can also access the official man pages on that site.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by nonbirithm on Tuesday May 02, 2023 @10:34AM (#35788103)
I agree with this. I was working on a project that was only available with Mercurial and I spent three days just trying to figure out how to not irreversibly corrupt my repo for a one-line change. I never figured it out and gave up since it wasn't super important.

I was happy when Atlassian finally sunset Mercurial, forcing those repositories to move to git. I'd rather all major source code hubs standardize on git since it's harder to contribute needing to learn different incompatible workflows.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by pabs3 on Tuesday May 02, 2023 @10:40AM (#35788198)
I recommend using git-remote-hg when dealing with Mercurial repos. Or git-cinnabar for very large ones like Mozilla's.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by MattJ100 on Tuesday May 02, 2023 @11:00AM (#35788521)
Corrupting your repo with a one-line change? Is there more to this story? A bug report, for example? It's not my experience of Mercurial at all.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by MetaWhirledPeas on Tuesday May 02, 2023 @11:37AM (#35789227)
Even if Mercurial is fine, Git is really good and is the standard in most cases. It's not worth confusing new hires with an alternative repo system when Git is this good, this common, and also happens to be FOSS.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by jcrawfordor on Tuesday May 02, 2023 @12:55PM (#35790567)
The usual argument for Mercurial, though, is that it's easier to use and more resistant to getting the local repo into odd states than Git. That tends to make Mercurial a better option for people without significant Git background, and definitely makes bad user experiences of that sort with Mercurial interesting.

I guess what I'm getting at is that Mercurial supporters tend to view it as distinctly better than Git, so sticking to Git just because of its widespread usage does feel like a sort of defeat... One could say similar about Fossil, a much more ambitious project that has faltered probably mostly due to Git claiming all the mind share.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by datavirtue on Tuesday May 02, 2023 @02:20PM (#35791967)
They will screw up their local branch exactly once in their life.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by m463 on Tuesday May 02, 2023 @05:06PM (#35794204)
I'm smiling a bit as today I've been trying to un-corrupt a git repo where lfs files were treated as repo files and vice versa. "where's by multi-mb binary, replaced by an ascii pointer file". how can I resolve ssh and https? ugh.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by rcme on Tuesday May 02, 2023 @10:25AM (#35787942)
Git is great. It’s FOSS, but that doesn’t mean it’s immune to a hostile corporate takeover. Take email for example. It’s an open standard, yet it’s usage is dominated by large corporate players.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by MattGaiser on Tuesday May 02, 2023 @10:26AM (#35787961)
The alternative is a spam and scam mess that would kill email.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by pmlnr on Tuesday May 02, 2023 @10:32AM (#35788058)
BS. There are and were (I lament dspam) excellent spam filters, plus if you enforce greylisting barely any spam gets through.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by elric on Tuesday May 02, 2023 @10:37AM (#35788135)
Indeed. And if we hit spammers with half the hammer that pirates have been hit with, it'd be a much smaller problem ... but for some reason, spam seems to be immune to legal action.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by meesles on Tuesday May 02, 2023 @10:42AM (#35788226)
Spam inflates numbers and ends up benefiting nearly everyone except the end user in the short-term: - Platforms benefit from larger activity volume, thus increasing their numbers and $$$ - FTC and other regulatory bodies get to take low-effort actions and tout the massive effects, ignoring the fact that they're slapping the ocean with a stick. - All the systems in between are charging each other for artificial traffic, resulting in a convenient ponzi-like situation. I wouldn't be surprised if large chunks of vendor (SendgridTwilio, cloud providers, etc.) revenues are from illegitimate business.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by wpm on Tuesday May 02, 2023 @11:37AM (#35789230)
I imagine a similar thing is happening in the phone space too. Scam calls are 99% of the calls I get on my cell phone now, and probably close to that for "revenue from calls" that the providers are raking in.

If I could spin up my own cell network like I could an email server and a domain, you bet that the big cell/telecom players would "blacklist" my domain for "spam" the moment they caught whiff and instantly make it almost useless, same as Gmail does.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by throwaway2037 on Tuesday May 02, 2023 @10:49AM (#35788333)
What about non-technical users? For my parents and siblings, using "free" online email from a major provider, like Google, Microsoft, or Yahoo certainly keeps them safer than old school POP3 (download to your PC). Email can get lost, scanning attachments was poor, and spam filtering was terrible, even by major Internet providers.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by pmlnr on Tuesday May 02, 2023 @12:58PM (#35790643)
Dude... IMAP is decades old. I used Squirrelmail webmail when gmail came out.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by throwaway2037 on Tuesday May 09, 2023 @10:55AM (#35875272)
In my pre-webmail experience, many ISPs did not offer IMAP as it requires them to keep email stored on their servers long term. The advantage of POP3: They force you to download it.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by rcme on Tuesday May 02, 2023 @10:34AM (#35788101)
You can run an LLM in your browser now. Pretty sure even a low parameter LLM is more than capable of detecting spam. And thats not even considering more specialized approaches.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by renewiltord on Tuesday May 02, 2023 @12:15PM (#35789883)
It is true that opt-in has bad UX. You can't easily "never send to spam".
Re:Let's Make Sure GitHub Doesn't Become the Only Option by jerf on Tuesday May 02, 2023 @10:52AM (#35788388)
Email has the issue that it wants to be an arbitrary person-to-person communication protocol, which communicates through servers. Therefore, if I want to email you, the behavior of your server is my problem. The set of such people I may want to communicate with is large and heterogenous.

Git does not have that problem. If four of my buddies want to get together and start a startup together, and I start out by simply setting up git on an SSH server, the four of us do not care that GitHub recently extended the Git protocol with a hot new feature that only works on Windows 13. We just use our git. I am not in the position of wanting to share arbitrary source code with everyone in the world. The relevant social circles are much, much smaller.

I don't know that I'd say git is immune to such takeover, but it is about as resistant as it is feasible to be.

The problem with GitHub isn't git. In fact, that is the least problematic aspect of all. The git repo, the branches, the tags, commit history, signatures, that's all the stuff that is not only easy to take with you, the git protocol all but stuffs them all down your throat with a "git clone". You have to ask git not to give you a fully independent copy of the whole repo.

The problem with GitHub is all the other stuff; the issues, the PRs, the conversations in there, the fact you gave out so many URLs pointing to github, etc. The thing that makes me most nervous about GitHub and my Go libraries is that if GitHub does turn evil, I've got "github.com" embedded in a lot of people's source code. I've decided it's not quite worth it to host on my own domains (plus I imagine people look askance at that anyhow) but it's a long-term concern of mine.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by geraldwhen on Tuesday May 02, 2023 @10:53AM (#35788394)
Git lfs is a lousy hack. I wish git had better support for large binary formats.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by TOGoS on Tuesday May 02, 2023 @11:28AM (#35789062)
The sad thing is that there's not much in Git's data model[1] that makes it bad for storing large binary blobs. An alternative implementation of Git (the program), or even a future version of vanilla `git`, could handle them just fine without the lfs hack, which I agree is horrendous, by using a different on-disk format for them and/or making sparse clones easier, and thereby remain 100% compatible with every other Git repository.

[1] There are some tweaks I would make, like using a standard Merkle tree hash function instead of sha1("blob "+size+"\0"+data), and a text-based encoding for commit and tree objects, but those are bike shed paint. I created a Git-like system based on these ideas that uses URNs and RDF/XML to make going 'under the hood' with a text editor a bit more pleasant than the experience with Git is, which is important because Git's tooling is far superior: https://github.com/TOGoS/ContentCouch/

Re:Let's Make Sure GitHub Doesn't Become the Only Option by haradion on Tuesday May 02, 2023 @11:53AM (#35789503)
Shallow/sparse clones help with some of the pain points there, at least around time to clone and local repo size.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by geraldwhen on Tuesday May 02, 2023 @04:21PM (#35793584)
I’ve got Jenkins configured to heck and back. Still a hassle though, and it’s clear it’s not a full solution.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by newswasboring on Tuesday May 02, 2023 @10:57AM (#35788460)
I don't get it, what exactly do you think is wrong with the email landscape? Its a standard protocol everyone can use, the only restrictions being when you start using other's services. Maybe I'm just not abreast enough on this.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by LanceH on Tuesday May 02, 2023 @11:26AM (#35789019)
I you want to send email from your server, you're entirely dependent on how the other servers run by the recipients view you. So if you have a bad IP address, they might not let your email through. The procedure for establishing yourself as a legitimate sender of email and not spam varies, and would need to be resolved with the operators of every server you might ever want to send mail to.

So you're running your mailing list which people have triple opted into, with confirmations and everything. Someone marks your email as spam and now everyone with a google address is bouncing. You contact google to resolve this and get a canned reply saying they've reviewed it, it's correct, and they will take no further action, and won't discuss it further. Good luck.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by MichaelZuo on Tuesday May 02, 2023 @11:33AM (#35789137)
How does this detract from email, the standard?
Re:Let's Make Sure GitHub Doesn't Become the Only Option by rcme on Tuesday May 02, 2023 @11:46AM (#35789391)
It impacts email as a standard because Google is a gatekeeper of what is supposed to be an open standard.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by newswasboring on Tuesday May 02, 2023 @01:29PM (#35791159)
Google is a gatekeeper for it's customers. Which is quite fair I guess. You are not entitled to anyone else's inbox
Re:Let's Make Sure GitHub Doesn't Become the Only Option by rcme on Tuesday May 02, 2023 @01:56PM (#35791596)
And Google has such a dominant position in the marketplace that your only choice is to use Google (or a handful of other large providers). That was the thesis: E-mail is an open standard dominated by large corporations.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by newswasboring on Tuesday May 02, 2023 @02:05PM (#35791749)
That is definitely not the only choice. There are services out there or you can also use your own servers. Google being big does not limit your choices on how to host your own email. Again, you are not entitled to other people's inboxes.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by danaris on Tuesday May 02, 2023 @02:14PM (#35791883)
I have a few VPSes and domains, and tried to set up email on one of them recently.

Jumped through every hoop, got rDNS, SPF, DMARC, and DKIM all configured correctly...only to find out that the major email providers (at least Google and Microsoft, which account for a depressingly large fraction of email accounts) have decided that the VPS provider doesn't meet their standards, and either auto-block or mark as spam anything I send.

So I'm left with the choice of trying to migrate my entire VPS to a different provider—after figuring out which one, if any, Google and Microsoft actually deign to bless as being worthy of sending email to them—or not host my own email.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by MichaelZuo on Tuesday May 02, 2023 @07:27PM (#35795622)
The email standard never specified or guaranteed access to the majority of inboxes (or any inboxes in fact). It's literally just a technical standard to conform to or not. Successfully transmitting emails to another inbox is completely orthogonal and based on the personal, or corporate, decisions of the sender, receiver, and anyone else in the chain.

There is no provision for a fair shake, special categories for new entrants, or anything similar.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by rcme on Tuesday May 02, 2023 @08:29PM (#35796186)
What value is an open standard if it can only be useful if you use an implementation from a large corporation. It’s a basic fact that email is only useful if your intended recipient can receive your message. If corporate gatekeepers are restricting valid usage outside of their walls, then it ceases to be an open standard. It’s like the difference between source available and open source.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by MichaelZuo on Tuesday May 02, 2023 @09:21PM (#35796531)
How does this relate to my comment?
Re:Let's Make Sure GitHub Doesn't Become the Only Option by i-use-nixos-btw on Tuesday May 02, 2023 @01:37PM (#35791290)
Nobody said it does. The clarification of it detracting from email the standard is yours.

It nonetheless demonstrates how Pareto allows popular providers to make decisions that negatively impact those who want to exercise the freedom granted to them. It doesn’t run in isolation, after all.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by MichaelZuo on Tuesday May 02, 2023 @07:19PM (#35795528)
Considering that the user, LanceH, was directly replying to:

> I don't get it, what exactly do you think is wrong with the email landscape? Its a standard protocol everyone can use, the only restrictions being when you start using other's services. Maybe I'm just not abreast enough on this.

I would say most readers would interpret that as in response to email, the standard.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by i-use-nixos-btw on Tuesday May 02, 2023 @07:48PM (#35795848)
The reply made it clear that the problem is with the email landscape, not the protocol:

> you're entirely dependent on how the other servers run by the recipients view you.

A protocol can be bulletproof. But spammers will spam, blockers will block, trusted platforms will control.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by nequo on Tuesday May 02, 2023 @10:18AM (#35787812)
CVS used to be the standard before Git. Arguably CVS as the standard was not better than no standard if no standard let you use decentralized version control.

But Git is pretty good, so it will take something vastly better to replace it.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by lolinder on Tuesday May 02, 2023 @10:31AM (#35788039)
My understanding is that before git a substantial portion of the industry used the "one big shared drive and shouting across the room to lock files" version control system. There was also SVN that was pretty popular pre-git.

I don't believe any version control system achieved as deep industry penetration as git has.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by liveoneggs on Tuesday May 02, 2023 @10:43AM (#35788250)
subversion was just as dominant as git is now. Not using version control at all is probably just as common as it was previously.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by throwawayx50223 on Tuesday May 02, 2023 @10:56AM (#35788447)
That matches my experience too. SVN and CVS was very common as far as I remember. More developers probably use version control now than before, but version control was considered part of "best practice" before git was released.

There were of course places that were late to switch. I remember one of my old work places used P4 due to legacy in the CI/CD pipelines, but many teams kept a "shadow" git repository in Bitbucket with a bridge to P4. After a while, the company finally switched to Github Enterprise

Re:Let's Make Sure GitHub Doesn't Become the Only Option by morelisp on Tuesday May 02, 2023 @10:54AM (#35788419)
SVN took over the hobbyist area rapidly due to its workflow/UI similarity to CVS, but P4 held fast professionally until at least 2015, as well as Source Safe if you were an MS shop. (And conservative places never switched off CVS at all.)
Re:Let's Make Sure GitHub Doesn't Become the Only Option by andreabergia on Tuesday May 02, 2023 @10:45AM (#35788280)
In my experience, SVN was _everywhere_ 10 years ago or so.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by pcthrowaway on Tuesday May 02, 2023 @10:58AM (#35788482)
I used SVN once for my capstone project 11 years ago, graduated that same year, and literally haven't encountered it a single time in my career since then.

It definitely wasn't everywhere 10 years ago (but github was). Do you mean 15-20?

Regardless, having completed a CS degree during the period SVN was supposedly everywhere and only encountered it once because someone in my capstone team knew how to use it, I'm inclined to think it didn't permeate everything the way git does now.

If I could complete a bachelors in CS without encountering it in any of my courses, I think it's safe to say git is much more ingrained in the field now (pretty much every syllabus I come across online for CS courses from the last 5 years has had some github links)

Re:Let's Make Sure GitHub Doesn't Become the Only Option by Klonoar on Tuesday May 02, 2023 @01:41PM (#35791349)
SVNs heyday is closer to 15 years ago at this point.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by JohnFen on Tuesday May 02, 2023 @10:51AM (#35788363)
> a substantial portion of the industry used the "one big shared drive and shouting across the room to lock files"

Perhaps, but I've never seen that done. The version control system that is in fashion changes over time, but for my entire multidecade career there has always been one.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by sigstoat on Tuesday May 02, 2023 @11:59AM (#35789610)
If you take a look at Rapid Development (published 1996), one of the classic mistakes it lists is not using version control. A number of other 90s and earlier texts lament people not using version control.

Personally, a guy I dealt with circa 2010 stood up in a meeting on building better site-wide development processes, and asked what the point of version control was.

So, you've been lucky.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by JohnFen on Tuesday May 02, 2023 @12:04PM (#35789701)
Sure, I remember when that complaint was often cited. I'm just saying that using a version control system was the most common case even then. It wasn't as common as it should have been, though, that's true. But using version control was still common well before git came around.

Now, if you go back to the mid '80s and earlier, version control was rare.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by test1235 on Tuesday May 02, 2023 @11:00AM (#35788517)
>one big shared drive and shouting across the room to lock files

yes ... how did you know we used visual source safe?

Re:Let's Make Sure GitHub Doesn't Become the Only Option by HWR_14 on Tuesday May 02, 2023 @12:36PM (#35790219)
By the mid-90's VSS supported exclusively locking files and requiring files to be locked before working on them.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by dabraham1248 on Tuesday May 02, 2023 @02:26PM (#35792062)
Well, kinda? We did that. Then we discovered that about 10% of the time it didn't actually lock anything. So we included yelling across the room into our "grab it exclusively from VSS".

Yes, we had MS support, and they looked into it, and eventually basically shrugged (I'm told. I wasn't the one working with them).

Re:Let's Make Sure GitHub Doesn't Become the Only Option by stcroixx on Tuesday May 02, 2023 @03:14PM (#35792688)
I've been in the industry for 25 years and have never seen it done that way anywhere. First place I worked used PVCS then migrated to Clear Case. The first free one I used was CVS.

I'd say each predecessor had about the same level of penetration, which was 'nearly all'. CVS->SVN-GIT. Git will be replaced. It's ripe for that - its interface is terrible, storage is now cheap, and many companies have no actual need for decentralized version control and the complexity that comes with it.

Easiest to use of the bunch is still svn. You can teach a developer everything they need to know in 5 minutes and there's 3-5 commands total you'll need to use ever. I never once saw anyone get into some nightmare state they needed help to dig out of like I've seen routinely with git.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by gspencley on Tuesday May 02, 2023 @10:24AM (#35787916)
CVS, subversion and mercurial are all VCS tools that I remember using throughout the years. Didn't Microsoft even have its own for a while? I swear I remember Visual C++ integration features back in the 90s / early 00s but I can't remember what it was called.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by david422 on Tuesday May 02, 2023 @10:40AM (#35788203)
Clearcase version control was a fun one.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by Sander_Marechal on Tuesday May 02, 2023 @10:27AM (#35787970)
Yes, MS Visual Sourcesafe (VSS). It was... not very good
Re:Let's Make Sure GitHub Doesn't Become the Only Option by grimjack00 on Tuesday May 02, 2023 @10:36AM (#35788130)
It was, however, a step up from the shared network drive with a bunch of zip files.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by politician on Tuesday May 02, 2023 @10:47AM (#35788296)
Debatable. You would come into work in the morning and find that VSS had been corrupted and needed to be restored to an earlier backup. This was a common occurrence.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by prepend on Tuesday May 02, 2023 @11:12AM (#35788745)
That the lovely common occurrence of someone checking out 1000 files and going on vacation.

I preferred just a normal folder, rsync (or some nt utils equivalent) and backups.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by wheelie_boy on Tuesday May 02, 2023 @10:44AM (#35788267)
they also had an internal source control system that they never released, which was a fork of perforce that they had purchased the rights to use and modify. Not sure if that's still in use in any projects.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by AndrewStephens on Tuesday May 02, 2023 @11:02AM (#35788558)
Back in the late 90s we used to call it Visual SourceSieve - code changes would just leak away through the holes. Words cannot explain how much of a step up git (or even SVN) was.

As I recall, the main problem was that VSS didn't have a proper server! Instead the client modified files in the repository directly using Window's file sharing, relying on locks to maintain consistency. This would have been a bad idea even in Window's file shares weren't slow and buggy.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by fanf2 on Tuesday May 02, 2023 @01:53PM (#35791559)
I believe Visual Source Unsafe used the same storage layer as early versions of Exchange, which would break catastrophically when the underlying file grew past 2GB. Less than ideal.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by HappyJoy on Tuesday May 02, 2023 @10:27AM (#35787966)
Team Foundation Version Control

Edit: And Visual Source Safe

Re:Let's Make Sure GitHub Doesn't Become the Only Option by ilikehurdles on Tuesday May 02, 2023 @10:27AM (#35787978)
Microsoft Visual SourceSafe
Re:Let's Make Sure GitHub Doesn't Become the Only Option by jiggywiggy on Tuesday May 02, 2023 @10:23AM (#35787901)
Is it though? Don't know anyone who likes merging or rebasing. Especially big merges. I don't know a solution. But I'm sure someone comes up with a significantly less painful way at some point.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by prettyStandard on Tuesday May 02, 2023 @10:42AM (#35788233)
I love rebasing.

As for dealing with merge conflicts, it's called

  - keep up to date with the branch your tracking
  - merge frequently
  - get on a call when you do have merge conflicts
  - avoid having multiple people working in the same files simultaneously if possible
The problem with merge conflicts is you have two people changing the same lines of code at the same time. So I would imagine if you wanted to improve the situation you would need an AI powered version control system that understood the intent of the previous developers. But that's not going to fix bad habits.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by yjftsjthsd-h on Tuesday May 02, 2023 @12:30PM (#35790102)
> As for dealing with merge conflicts, it's called

That sounds like a lot of words for "try really hard to avoid having merge conflicts, because they suck to deal with"

Re:Let's Make Sure GitHub Doesn't Become the Only Option by jdmichal on Tuesday May 02, 2023 @10:41AM (#35788209)
I've used many different version control systems. Git is, by far, the best at merging and avoiding conflicts to start with. I believe it's because it can often work from the basis of a common ancestor commit, so it's able to perform three-way merges instead of two-way merges.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by HWR_14 on Tuesday May 02, 2023 @12:38PM (#35790254)
Wait, avoiding 3-way merges and instead only allowing 2-way merges has been on my list of "advantages of Mercurial that are sadly lost to git" list for a while. Can you expand on what you're saying?
Re:Let's Make Sure GitHub Doesn't Become the Only Option by jdmichal on Tuesday May 02, 2023 @02:48PM (#35792343)
Three-way merge might not be the correct term. I mean it as in the three versions being "original", "version-a", and "version-b". Original is the most recent common ancestor of version-a and version-b. So the system can generate clean diffs based on that original version during the merge.

I've seen other systems essentially say, "Oops both versions modified this file... Good luck!" It didn't matter that the modifications were to very different parts of the file. I've never seen that in Git. Any merge conflict I've gotten in Git has been a true potential conflict, even if the resolution is straight-forward from my perspective.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by HWR_14 on Tuesday May 02, 2023 @03:01PM (#35792515)
Ah, that's a standard merge but a 3-way diff. Many DVCSs have that (including Mercurial).

A 3 way merge would have "original", "version a", "version b", and "version c", where "original" is the common ancestor of a, b and c. Mercurial disallows merges like this, but git supports them. I have no idea why git allows it.

But yes, older VCSs ignored the "original" concept, which meant diff tools could just pop up "a" and "b". Which is just a way worse idea than including the original as well.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by throwawayadvsec on Tuesday May 02, 2023 @10:26AM (#35787960)
well merging two wildly different of files is going to be complicated using any tool, git is not the issue there, there isn't a million ways to handle this
Re:Let's Make Sure GitHub Doesn't Become the Only Option by dmoy on Tuesday May 02, 2023 @10:50AM (#35788352)
Right it's a use type thing.

If everyone develops from master branch and makes small incremental changes, no problem even if it's git.

If everyone develops from their own branches and goes off and does their own thing for a month, but those things are all in totally separate areas of the codebase, not as much of a problem either.

If everyone is developing in their own branches for a month, and they're working on overlapping things, and they aren't communicating? Then you get merge problems

But it's not really a merge problem, it's a communication problem. (And it's not git-only, you see merge problems even in perforce when people go dark for a long time and come back with a huge change that's got conflicts on 50% of the lines now)

Re:Let's Make Sure GitHub Doesn't Become the Only Option by nirimda on Tuesday May 02, 2023 @10:53AM (#35788398)
There's three ways. One is the git way, which is to let people do whatever and then ask them to handle it afterwards. The next best is used by some other annoying system I used early in my career, which is to require people to check out a file before they can get write permission on it, and only allow one person to have write permission at once, so that there's no real risk of merges. And the worst of all is to just let whoever comes later overwrite whatever was there before.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by jcranmer on Tuesday May 02, 2023 @10:48AM (#35788323)
Mercurial's phases and changeset evolution make specifically rebasing far less painful. git rebase -i is downright antediluvian in comparison.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by prepend on Tuesday May 02, 2023 @11:15AM (#35788809)
Merges are hard and I’ve never seen a system that removes the difficulty. I actually think git is the best because it’s easier to branch and update than many others (a pull takes a second to refresh vs quite a while for large repos with svn).

I was using ClearCase for a few years and they had a really nice visual merge tool, but the complexity of the merge was great because they were so infrequent. I made a mistake and let someone find out I could merge and ended up getting sucked into these quarterly multi-day merge sessions that made me feel like a guild navigator stressing about breaking one of thousands of changes from 50 people over 90 days.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by adastra22 on Tuesday May 02, 2023 @11:38AM (#35789240)
The solution is darcs’ patch-theory model of development, currently being pushed forward by pijul.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by gavinhoward on Tuesday May 02, 2023 @12:14PM (#35789855)
I am making a VCS to compete against Git and Pijul.

The patch-centric model of Darcs and Pijul is insufficient. You also need to remember where patches came from. If rewriting a patch does not keep its provenance, you're also in for a world of hurt.

But even that is not sufficient. You need to have more context than even the patch-centric model gives you.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by adastra22 on Tuesday May 02, 2023 @03:08PM (#35792594)
Please share when it is ready!
Re:Let's Make Sure GitHub Doesn't Become the Only Option by gavinhoward on Tuesday May 02, 2023 @03:21PM (#35792769)
Absolutely! I am planning to make a "Show HN" my official announcement, but only after it is self-hosting and has enough features to replace my Gitea instance.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by JohnFen on Tuesday May 02, 2023 @10:53AM (#35788399)
> But Git is pretty good, so it will take something vastly better to replace it.

Git is fine, but honestly, my favorite of the several I've used over the years is still svn.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by forrestthewoods on Tuesday May 02, 2023 @11:32AM (#35789127)
> But Git is pretty good, so it will take something vastly better to replace it.

Correction: Git is super mediocre, but sufficiently wide spread it will take something vastly better to replace it.

Don’t confuse inertia with goodness.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by MetaWhirledPeas on Tuesday May 02, 2023 @11:41AM (#35789304)
Git is solving a very complicated problem with a command line tool. Don't confuse a complicated problem with a mediocre application.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by forrestthewoods on Tuesday May 02, 2023 @01:05PM (#35790768)
Git is a mediocre CLI, imho, ymmv. GitHub I don’t have a strong opinion on.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by nequo on Tuesday May 02, 2023 @05:14PM (#35794305)
But Git is not only the porcelain, it’s also the plumbing. Do you think that the plumbing is super mediocre too?
Re:Let's Make Sure GitHub Doesn't Become the Only Option by forrestthewoods on Tuesday May 02, 2023 @10:48PM (#35797163)
I don’t know what that analogy is supposed to mean. I don’t think analogies are necessary or appropriate here.
Re:Let's Make Sure GitHub Doesn't Become the Only Option by nequo on Wednesday May 03, 2023 @07:47AM (#35801180)
This is the terminology that Git uses. Porcelain is the UI, whether it’s the basic CLI, Magit, Fugitive, or anything else. Plumbing is Git under the UI.

Are you saying that the CLI is bad, or that Git’s underlying concepts and data model are bad?

Re:Let's Make Sure GitHub Doesn't Become the Only Option by forrestthewoods on Wednesday May 03, 2023 @05:02PM (#35807761)
Git’s CLI API is definitely bad.

I think the plumbing is probably in-between poor and bad for most projects. It’s maybe great for Linux. However almost all projects are effectively centralized so the D in DVCS is a waste. (Offline/local support and fully distributed are different). I think source control should make it impossible for 99% of users to shoot themselves in the foot. And Git is still terrible at large binary assets, even with Git-LFS.

I use Git + GitHub for my personal projects. It’s mediocre but tolerable. Git is insufficient and not used for every professional project I have ever worked on. YMMV.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by nequo on Thursday May 04, 2023 @08:58AM (#35814550)
Yeah, that makes sense. The CLI is definitely confusing. Every now and then you have draw on a book of spells to use it. I find it more comfortable with Magit but not sure if that makes up for all of the problems with the CLI.

What VCS would you use if it was all up to you?

Re:Let's Make Sure GitHub Doesn't Become the Only Option by forrestthewoods on Thursday May 04, 2023 @01:34PM (#35819172)
> What VCS would you use if it was all up to you?

Almost 100% of game devs use Perforce. Git is a non-option.

BigTech all use highly custom source control systems. They have some nice properties.

My stance isn’t that we should use something other than Git per se. It’s that Git is a local maxima, and it kinda sucks. And I think the industry would be healthier if people agreed Git sucks.

Features I care about:

* Terabyte scale sparse checkouts * Ten terabyte scale full checkout * Petabyte scale history * Lossless history. * Automatic cloud/remote backups of every commit * Trivial for low-tech people to use (Perforce achieves this) * Cross-branch file locking for non-mergeable assets

Things I don’t care about:

* Distributed. Defacto centralized with forking is all I need. * Rewriting history. Linux needs it, I don’t.

There are of course lots of things I do like about Git. It’d be good if Git and Perforce had some competition. There’s a market opportunity for it imho.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by mihaic on Tuesday May 02, 2023 @11:31AM (#35789112)
I remember using Perforce and Accurev about 10 years ago, and they were miles better than Git in terms of abstraction and feature set. I often miss being able to work on multiple branches with partially uncommitted local work for instance.

I do want the open-source world to improve and if we merely build on top of git's abstraction, how can we have any progress then?

Re:Let's Make Sure GitHub Doesn't Become the Only Option by haradion on Tuesday May 02, 2023 @11:58AM (#35789586)
For the specific use case you're describing, I've found `git worktree` to be very useful.

Overall, at least when it comes to features, I've actually had the opposite experience. That said, I'm one of those people such that you can pry `git rebase` out of my cold, dead hands, so it's that feature specifically that I really miss when I have to work with Perforce.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by ubertaco on Tuesday May 02, 2023 @02:55PM (#35792429)
Salesforce uses Perforce internally, and it's a _massive_ source of problems for their giant monorepo precisely because there's no lightweight branching, so among the 1500+ developers working on the same codebase, _someone_'s always checking broken crap into the same branch all the time and causing huge headaches for everyone else.

When I left, they were investing a ton of time and developer hours into trying to duct-tape git onto their workflow by having smaller groups of developers share cached copies of their huge Perforce repo, and shunting the inevitable merge conflicts onto someone else and hoping for the best.

I spent a considerable amount of time training folks at my acquisition how to work in this environment, and roughly 70% of that time was "yes, Perforce _is_ weird and confusing and annoying, and yes, it _would_ be better if we had lightweight branches, but instead we're stuck in the version-control stone age of Perforce, so here's the complex process you can try to go through to un-break your own local codebase temporarily until someone else has fixed the broken crap they checked in."

Re:Let's Make Sure GitHub Doesn't Become the Only Option by eesmith on Tuesday May 02, 2023 @11:45AM (#35789372)
> At some point every industry grows up and standardizes on something, anything, because any standard is better than no standard.

What's the standard programming language? The standard editor? The standard database?

> launching a competing standard at this point isn't going to make things better, the best case scenario is that it fragments the industry.

People keep coming out with new programming languages, new editors, and new databases.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by Klonoar on Tuesday May 02, 2023 @01:43PM (#35791393)
The standard editor, if one had to give an answer, is probably VSCode at this point.

Likewise the standard DB may be Postgres.

Others exist but they’re certainly not the recommended defaults you find people giving out nowadays.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by eesmith on Tuesday May 02, 2023 @02:03PM (#35791712)
But no standard programming language, yes?

VSCode was not the standard seven years ago. ("In the 2016 Developers Survey of Stack Overflow, Visual Studio Code ranked No. 13 among the top popular development tools, with only 7% of the 47,000 respondents using it" says Wikipedia).

If lolinder's thesis is true, then that means it can take over 50 years before the industry decides on a standard. Which seems rather a long time for that statement to be meaningful. Because within 10 years maybe it will all change again.

FWIW, I've mostly used SQLite as my DB.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by Klonoar on Tuesday May 02, 2023 @03:22PM (#35792775)
What on earth does 7 years ago have to do with 2023? Look at the 2022 survey, not one from 2016:

https://survey.stackoverflow.co/2022/#most-popular-technolog...

VSCode is overwhelming at a staggering 74%. ;P

Re:Let's Make Sure GitHub Doesn't Become the Only Option by eesmith on Tuesday May 02, 2023 @04:29PM (#35793729)
Git is certainly by far the de facto standard VCS. But I don't think lolinder's reasoning for why that is so has strong support, as it doesn't explain why other areas haven't already achieved the same standardization.

lolinder wrote "At some point every industry grows up and standardizes on something, anything, because any standard is better than no standard."

Either there was a standard editor before VSCode or there was not.

If there was a standard editor before VSCode, then it's clear that standards can change, which challenges lolinder's proposal that "launching a competing standard at this point isn't going to make things better". The VSCode developers likely thought it would make things better.

If it was no standard editor, then it took about 50 years for the industry to decide on one (dating from the late 1960s to 2016, when VSCode was definitely not the standard).

Leading to my observation that the "at some point" can take decades, and implies the urge to have a standard is not all that strong.

My memories of the 1990s was the CVS was the de facto standard, like how VSCode is now for text editors. Yet people fragmented the industry with SVN, BZR, Git, BitKeeper, Git, and more - because because they thought they could make things better. And at least one of them was right.

I'm therefore not so confident about rejecting launching an alternative to git. My limited understanding of Fossil, for example, tells me there are better approaches than git. (Then again, I'm a Mercurial user, so I already have my own preferences. ;)

Re:Let's Make Sure GitHub Doesn't Become the Only Option by emrah on Tuesday May 02, 2023 @01:50PM (#35791512)
> Git is far from an ideal solution, but it has emerged as the standard way

Humans are such a weird species. The juxtaposition of the two arguments ("not ideal" and "the standard") is crazy to me. If it's not ideal, let's move away from it, not standardized on it. Is that too much to expect? :)

Re:Let's Make Sure GitHub Doesn't Become the Only Option by jiveturkey on Tuesday May 02, 2023 @02:29PM (#35792116)
English units (feet, pounds) are not ideal, and we have a better solution, yet ...
Re:Let's Make Sure GitHub Doesn't Become the Only Option by jiveturkey on Tuesday May 02, 2023 @02:43PM (#35792288)
> I disagree that the dominance of git is a problem.

ok but that's not the argument of the article, so you aren't disagreeing with TFA. Maybe you're disagreeing with another top level comment.

TFA is arguing that the dominance of git hub is or is becoming a problem.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by lolinder on Tuesday May 02, 2023 @04:39PM (#35793864)
And there's an entire section that argues that git becoming entrenched as the standard is part of the problem with GitHub. That's what I was replying to.

> git itself, while not owned by GitHub, is even more popular. This is largely because of GitHub’s popularity and in spite of git’s poor UX. It would be nice to move beyond git one day and have a better experience for managing complex codebases, and not on GitHub’s timeline.

> ...

> I want to underscore this because I think it’s important: git and GitHub’s symbiosis are holding us back as an industry.

> ...

> Other version control software exists that doesn’t need a separate company to make the code accessible from the web or makes dealing with conflicts easier. We as an industry cannot benefit from these alternatives if we continue to use GitHub this heavily.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by jiveturkey on Tuesday May 02, 2023 @07:08PM (#35795420)
thanks. i somehow glossed over those bits. i guess because i agree that the dominance of github is a disaster, so i was focused on the parts of TFA that i agree with.

like you, and i guess contrary to the article (again, like you), i think git itself as lingua franca is fine and maybe even great. certainly it has warts, some of them substantial, but what doesn't. we've come a long way since CVS and (shudder) SCCS.

Re:Let's Make Sure GitHub Doesn't Become the Only Option by pmeunier on Tuesday May 02, 2023 @03:09PM (#35792613)
This is only true for alternatives to Git that are roughly equivalent in terms of complexity and time to learn. This wouldn't hold for an actual improvement (in productivity and training time), just like Rust, Zig or even Go are oven C++ and Java (the industry standards).