251–260 of 519 posts
Earlier quoted context omitted.
They're really not, given they're running on Azure.
Is there any data on Azure being terrible with stability? Would love to see data than anecdotal stories.
I'd never put my data on anything owned by Musk. Period. I'd take lower availability from GitHub or a worse alternative (feature-wise) than move Origin.
Hi all, my name is Tomas. I am one of the developers on Origin, and I was one of the founders of Graphite ( https://graphite.com ). Happy to answer any questions about Origin or source control in general!
Earlier quoted context omitted.
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.
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.
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 quoted context omitted.
How long term are we talking here? Github was acquired in 2018...
I think GH/Microsoft got caught by surprise to the huge usage number increase as a result of LLMs. Microsoft started rolling all of its DCs to OpenAI around 2019-2020 to begin LLM training, then we saw a huge GH increase in late 2024 and Azure was just out of capacity for infinite GH scale.
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.
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?
Instead of creating one more centralized alternative, it's best to invest all effort into a decentralized solution, like Radicle[1][2] or federated Forgejo[3][4]. [1] https://radicle.dev/ [2] https://radicle.network/nodes/seed.radicle.dev/rad%3Az3gqcJU... [3] https://forgejo.org/ [4] https://codeberg.org/forgejo-contrib/federation/src/branch/m...
I feel like this misses the value of something like Github or Origin entirely though. There's nothing terribly difficult about hosting a git server. The UX and pull requests capabilities are a little involved, but there are alternatives today. What makes Github special is the ecosystem and integrations. Sentry, Linear, and so many other tools have special UX around Github. You need centralization (or at the very leas…
Like a specification[^0], which is exactly what ActivityPub is and what federation in Forgejo is built around?
[0]: https://en.wikipedia.org/wiki/ActivityPub
I'm sure that sentry and co could spend a few bucks and commit a KPI in one of their upcoming quarters to figure out the activity pub spec and support integrating with it if their hearts desired. It's a chicken egg problem and we all know chickens exist. It's clear that the centralized model is getting left behind, especially as the EU is moving away from US services and they continue to invest in open source, European-based alternatives like Codeberg and Forgejo.
Does it support jujutsu natively?
We are very interested in this. If anyone can put us in touch with the JJ maintainers we would love to chat!
But just saying that I would probably argue against any new forge at my workplace if it didn't adopt the jujutsu model for changes. While agents can wrangle git better than 90% of developers, jujutsu just works much better for both.