How about neither?
Man I wish we stuck with Subversion at this point.
How about neither?
Man I wish we stuck with Subversion at this point.
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.
I use it quite a lot and the first time I actually witnessed downtime myself was yesterday.
github for large project that rely on CI tool is a nightmare (cost, downtime, etc.)
I'm guessing you dont know about the github actions bug that was running and endless loop consuming 100% cpu costing orgs insane amounts of money that they didn't fix for 3 years.
It also shows there’s a fundamental problem with their architecture or their development pattern to have these sorts of issues so frequently.
Anecdotally: at work I saw quite a lot of github-uptime-related issues, and because they're the central host for everything they become *cough* load bearing for a huge amount of the company. Stability and performance has been dramatically worse than the self-hosted phabricator+gitolite before it.
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.
Earlier today our app, used by a handful of actual production customers, went down for 30 minutes due to a GCP migration to a new project and we screwed up a secret in prod. This was an all hands on deck firedrill with 5 whys and incident reports and chaos.
Github has been having major production outages routinely! There are companies who can't release, can't build, can't view issues, basically can't work. I'd imagine most orgs using Github have been forced to move off of them or create an alternate approach to actually get shit done.
I use GitHub a lot and it does what I need well enough, but I wouldn't spend money on the level of service or performance it generally delivers.
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.
So there is more to lose than just the service being unreliable.
As a person he's either a poser or a neo-nazi. As a government agent he's responsible for many deaths and as of yet untold harm. Tesla was one of the earliest EV manufacturers, but these days they're overpriced and will be remembered for panel gaps and being destroyed by a car wash. SpaceX has done a lot for that sector, but will mostly be remembered as the company that fucked astrophotography with 10s of thousands of satellites. And Twitter has been dragged into irrelevance so badly it was being called a "reverse startup." Neuralink seems to be going nowhere...
Where's the benefit?
Among many other things he has openly suggested that the EU should be abolished and national sovereignties restored and donated to parties that tow that line.
But the EU isn't obsessed with "winning" or "being number one", like the US, which is number one in almost no area regardless.
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.
Git became popular because Linus Torvalds created it and it's used for the Linux kernel. If it can succeed there then it's battle proven for sure and that's why people pick it. Almost no one is working at that scale though so don't sweat it. Use what you want.
Mercurial was pretty nice back in the day and I think people still use it. If I was going to use something other than git these days, I'd probably take a look at fossil. That thing is so damn cool. You don't even need something like github with that because it's literally built into the fossil binary. And when I say binary, I mean a single, standalone binary for the whole thing.
/s