891–900 of 1001 posts
I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say). Nobody should cry over a SaaS, of all things. But GitHub has meant so much more to me than that (all laid out in the post). I have an unhealthy relationship with it. Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know. We've been…
Earlier quoted context omitted.
And you, my father, there on the sad height, Curse, bless, me now with your fierce tears, I pray. Do not go gentle into that good night. Rage, rage against the dying of the light. We can't really change the tide lest we be King Cnut - but we can at least take the time and effort in the things we do to fight against entropy - bring more order and durability into our lives. Or perhaps another adaptation: God, grant me…
We can; the tide changed to where it is now and can change again - and somebody will change it. People need to stop bemoaning it, and think and do something. The enshittification is an idiotic, failing, extremely short-sighted strategy. It's a huge opportunity - your competition has stopped investing in its product, fired its talent, treats its customers with utter contempt, and is managed by imbeciles. Who is a bett…
Earlier quoted context omitted.
> People are ANGRY about the AI boom impact right now and "microslop" is trending harder than "M$" back in the day. The writer of this blog post is Mitchell Hashimoto, and he has posted positively about AI, so that doesn't track at all. The reason people are talking about it is because the decline is rapid. That's worse than the raw downtime. There's a sense that it will be even worse in a year. I'm not a fan of AI e…
It's contagious negativity.
Do you have anything to contribute other than "everyone is irrational but me?"
Earlier quoted context omitted.
I used to work at GitHub. I think you should find a new job. Before Microsoft came along, the entire company was aligned from the bottom to the top around the goal of delivering a single great product. As soon as they bought us, that changed; there were now lots of ways for an individual to succeed at GitHub-the-division-of-Microsoft that had nothing to do with GitHub-the-product. Now GitHub doesn't even have its own…
This isn't a surprise at all. I saw the exact same thing at Meta. The incentives are so strong to improve your individual performance that it's hard to resist, literally hundreds of thousands of dollars at stake. Now with the fear of constant layoffs at Microsoft and Meta too, it's even more critical for individual engineers to optimize their performance review or you might lose your job. Sadly this is hard to line u…
If you optimize for performance reviews, you'll make a lot of money, yeah. But you'll eventually find yourself overemployed and incapable of keeping up with that gambit anymore. Or, you'll find yourself doing something you never wanted to do. In extreme cases, it's like those people at Palantir in that post last week, realizing they're the bad guys. Usually it's just looking at your calendar on Monday evening, seeing a wall of meetings from 4PM to 9PM, and telling your kid you can't go to the park today.
Meanwhile, the "product people" I know well are all doing really cool stuff during the day, then going home to enjoy their lives. They don't make as much money, but they're happy.
Quote that one Wu-Tang song today, and you'll be quoting that one Talking Heads song in a couple years. I guess.
> To the "Git is distributed!" crowd: the issue isn't Git, it's the infrastructure we rely on around it: issues, PRs, Actions, etc. A suggestion: use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg. It saves issues, PRs etc in git itself (not on a branch - on a specially crafted ref). It offers two way sync with a lot of providers. Other VCSes like fossil store issue…
git-bug is great but it doesn't handle PRs nor does it have a method for users without commit rights to submit bugs to the project. I know they're working on the latter (something with the web UI?) but until then you still need some kind of public infra for issue management if you want the general public to be able to submit issues. I use it for my project[0] to keep issues centralized with the repo, but I still use…
I can appreciate Hashimoto's genuine feelings about Github, and the world of open-source software development that it opened for him and that he spent a significant chunk of his life participating in. On the other hand, I can't help but think that some of this heartbreak would have been avoidable, if only he possessed more of the Richard-Stallman-esque attitude that non-free software is inherently suspect and unethic…
I think that model works well when it comes to code, but I don't think the non-free software movement ever really figured out how to deal with services and data. Even if GitHub was completely 100% GPL Free Software... the user accounts and everyone's comment history and stuff lives on a database somewhere. The servers are running somewhere. That's where the community is.
Even if you could take GitHub and spin up your own fork running the exact same software, the community isn't there. The interactions aren't there, the history isn't. It's like building a clone of your childhood house and wondering why your young parents don't magically appear in it.
Earlier quoted context omitted.
As someone who relies on it for all of my workflows at a normal job, core functionality issues result in me not being able to get work done on at least a weekly basis reliably at this point, and it's been that way for months. The things aren't profile pictures not loading in saudi, they're botching merge jobs, git/api operations being down, pull requests not loading, etc. And that's on top of the plethora of UI bugs…
This. I feel like there should be a developer uptime index that measures these things that we use every work hour. And it should not depend on their status page which seems to take a while to catch up when there's an actual outage.
You can pick whichever services you feel fall into this category in the top.
For the bundle I chose, there have only been 3 totally clean weeks so far in 2026 :/
I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say). Nobody should cry over a SaaS, of all things. But GitHub has meant so much more to me than that (all laid out in the post). I have an unhealthy relationship with it. Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know. We've been…
Earlier quoted context omitted.
Hi there! Longtime fan and hubber here. It's okay to have emotions. I have similar emotions. I'm GitHub User 22723 which is effectively the same as you (considering there's ~180m GH accounts nowadays) My version of your post reads differently: "GitHub only gets better if people who give a shit stick around to make it better" Walking away would be easy. I felt that way when I left Heroku ~six years ago. I left that jo…
I used to think people who said Github had become very unreliable were exagerating, but I can't miss it now. If you want to keep people, you have to actually go down less. It's interesting that internally you had a very different experience with Salesforce buying Heroku and Microsoft buying Github. From the outside it appears to be analagous (except github is degrading quicker than Heroku did?)
This pops up on here frequently. People misremember the Heroku timeline with Salesforce. Most of Heroku's growth and glory days happened after the acquisition. Salesforce actively invested in it and turned it into the powerhouse that people remember today.
At some point, they stopped, and it's not clear why.
People flip the order of the first two and remember it as "Salesforce acquired Heroku and then they went on a downward spiral" but that's not really what happened. There were many years of growth in between, including the period that almost everyone who remembers Heroku fondly remember it for.