GitHub is a mess so lets throw our code into a Musk owned enterprise, famously a different shade of mess?

How about neither?

Man I wish we stuck with Subversion at this point.

I feel like the "GitHub is a mess" conversation is a little forced at times - I spend a significant portion of my work day in GitHub and while there have been an uptick in outages lately, it still feels like a very solid platform.

I guess I personally wouldn't categorize it as a "mess" and the conversations I read about it here make me think I'm using an entirely different product than everyone else.

▲

camdenreslink 2 hours ago | parent | next [-]

When you work at an enterprise that depends on Github, frequent outages are actually a pretty big deal and begin to impact productivity in a real way.

▲

whstl 2 hours ago | parent | prev [-]

I love to hate on Github/Microsoft as much as the next person, but considering the insane amount of code being pushed to it every day, I'd say they're doing quite well.

▲

maccard an hour ago | parent | next [-]

I disagree. They’ve been struggling with up time for a long time, this seems more related to their move to azure than anything else.

It also shows there’s a fundamental problem with their architecture or their development pattern to have these sorts of issues so frequently.

	▲	infamouscow 13 minutes ago \| parent [-]
		I'd emphasize their practices as being the culprit. Migrating to different cloud vendors, while difficult, is something that people have done many times before. There's only finite number of incongruences that appear when moving cloud vendors. It's rather difficult to explain the ongoing problems several years after the fact. Anyone that's worked at a startup knows that one of the best things about it is reflecting on all of the asinine, if not genuinely stupid policies of your previous employer so as not to repeat them. Without any insider knowledge, the practices and procedures GitHub had prior to acquisition probably look nothing like those post-acquisition.

▲

2 hours ago | parent | prev [-]

[deleted]

▲

jm4 2 hours ago | parent | prev | next [-]

Git is objectively better than Subversion. The problem is we are conflating a widely used hosting service with the underlying SCM. We don't need github to use git successfully. Sure, it's nice, but you can install Forgejo or something, which is the exact same boat we were in with Subversion + Trac. You can have that experience right now if you want to.

What github is good for is discovery, getting contributions on open source projects (because it's so popular), and integrations. If you wanted to, you could host your open source project on Forgejo and use github as a mirror just to benefit from the visibility and get contributions.

▲

spiderfarmer 2 hours ago | parent | prev | next [-]

Just the association with Musk will mean no EU company should use Cursor or its products.

▲

bmitc 41 minutes ago | parent | prev | next [-]

Or Perforce. Perforce, in my experience, just worked. It also has sane conceptual names for things, a good CLI, SDKs, visual tools, cool features like workspaces that Git completely lacks, etc.

▲

trollbridge an hour ago | parent | prev | next [-]

You do know you can run git on your own machine, on pretty much any Linux/Unix based server, run it entirely peer-to-peer if you wish... or use Gitlab, including self-hosted Gitlab, or one of many other Git based servers?

	▲	cryo32 10 minutes ago \| parent [-]
		Yeah. I just don't really like git. The user interface is dog shit, merging is nasty, it's really easy to blow your own toes off and it's generally horrible. The only reason it got anywhere was github.

▲

janfoeh 2 hours ago | parent | prev | next [-]

That makes very little sense to me. When your Subversion server is gone, you're hosed. When your Git forge is down, you take any old SSH shell account anywhere, push and keep working.

▲

cryo32 2 hours ago | parent | next [-]

The last subversion server I had was on prem on VMware. There wasn’t any unscheduled downtime in a decade.

▲

jaccola 2 hours ago | parent | prev [-]

I like Musk companies more than most here it seems, I think he’s a net positive to the world. But (admittedly sans hard evidence) he absolutely gives me the vibe he’d train on my source code without my permission. I simply don’t trust him in this arena.

So there is more to lose than just the service being unreliable.

	▲	twalla 2 hours ago \| parent [-]
		whatever you say bro - https://www.thelancet.com/article/S0140-6736(25)01186-9/full...

▲

seany 3 hours ago | parent | prev | next [-]

if we're totally switching tooling, lets at least go to mercurial instead

▲

gaigalas 2 hours ago | parent [-]

If we're switching, we should probably go to fossil instead.

▲

yjftsjthsd-h 2 hours ago | parent [-]

That actually does make sense seeing as fossil bakes in issues and wikis and all that other stuff that makes it hard to use plain git.

▲

WorldMaker an hour ago | parent [-]

GitHub's wikis are just git repositories with folders full of Markdown files. That's the easiest thing to pull out of GitHub. Just git clone the wiki repo. At that point I often just use a git headless merge to merge the second repo into the main repo under a docs/wiki/ folder or similar.

As I recall, in GHE I remember finding that you could even turn off the repo's wiki at that point and then reset it to point to your docs/wiki/ folder and still have the Wiki interface but pointing it to a branch in the same repository. That was a while ago and I don't know if it is still supported in GHE. I also remember it was work managing that wiki branch because Wikis didn't directly support PR workflows if you have branch protection policies. Also from the documentation it doesn't look like it is supported in Public GitHub right now, which seems a shame to me, as someone who likes all documentation in the same repo as the source. I haven't needed Wikis in public GitHub much, so I haven't tried to do anything like point them to a main repo branch.

	▲	yjftsjthsd-h an hour ago \| parent [-]
		That's fair. You could also just put the wiki in a different branch if that's your style.

▲

z_rho_one 2 hours ago | parent | prev [-]

This feels like an attempt to get more of Musk's non-coder fans to start vibe coding slop-products. "You can now code with Grok via Cursor and host your code on Origin, all without leaving Daddy Elon's ecosystem."