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…
Ghostty is leaving GitHub
731–740 of 1001 posts
Re: Ghostty is leaving GitHub
#732The author is entitled to his feelings. People can host their projects wherever they like. However, this is also a huge drama about basically nothing. GitHub is actually much more useful now than it was in its heyday (when it had far fewer features to go wrong).
Re: Ghostty is leaving GitHub
#733There's probably a few more to be added there now.
Re: Ghostty is leaving GitHub
#734Earlier quoted context omitted.
> insider perspective on this I do not work at MSFT but I don't feel that I need insider perspective to understand what's going on. GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters. Everything becomes the numbers game. Microsoft, Oracle, VMware, CA (where software goes to die), Salesforce, the list goes on.…
I'm afraid this is a form of reversion to the mean. Successful startups are made of exceptional people: the founders, the initial investors, the first employees, the first clients. But when they get acquired by much larger companies, they are necessarily diluted in pool of people that are more "normal", less exceptional. This includes the customer base that is more "normal" as well. Slowly but surely, the extraordina…
Re: Ghostty is leaving GitHub
#735Earlier quoted context omitted.
Exactly this. Even though I don't use git-bug anymore, I'm still a sponsor. I desperately want an issue-tracker-in-.git to become a standard. Issues and CI are the only lock-in. The latter is legitimate because you're using someone else's CPU, but every developer has the tooling to "git diff" and write comments if we could just agree on a format.
I have trouble wrapping my head around how to make it so the public can create an issue in your git repo.
Sure, a little more complicated than “Create Issue”, but not that much for devs. We could even simplify the workflow with e.g. git-issue or something like that, similar to e.g. git-send-email.
git issue init “There is a problem”
git issue push
git issue get 6 # short for issue@{6}Re: Ghostty is leaving GitHub
#736Earlier quoted context omitted.
> insider perspective on this I do not work at MSFT but I don't feel that I need insider perspective to understand what's going on. GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters. Everything becomes the numbers game. Microsoft, Oracle, VMware, CA (where software goes to die), Salesforce, the list goes on.…
This is a general observation, no hard data, but I find there seems to be a wall at 2 years after an acquisition. By 2 years a lot of the best talent leave the company entirely or go somewhere else in the company. Things can cruise along just fine for a bit, but as the institutional knowledge slowly leaves it gets worse and worse. Couple that with the bureaucracy and insanity of a global mega-corporation, the quality…
Re: Ghostty is leaving GitHub
#737Earlier quoted context omitted.
> insider perspective on this I do not work at MSFT but I don't feel that I need insider perspective to understand what's going on. GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters. Everything becomes the numbers game. Microsoft, Oracle, VMware, CA (where software goes to die), Salesforce, the list goes on.…
It's just beancounters doing what they do best, counting beans and screwing up what was previously alright.
Re: Ghostty is leaving GitHub
#738During one of the x threads where Mitchell was (legitimately) complaining about Github, there were a couple replies suggesting that GitHub should hire him to be their CEO. And I remember seeing that and thinking "huh... not at all a bad idea." There is a specific kind of leader that can turn such ships around, and they are strong in their convictions, and aren't just "managers", but visionaries coupled with strong ex…
The problem is that Github does a lot . However, I consider that there is still not a great UI for the core service, in special for a complex project. In the other hand, I bet jujutsu has the best basic take, and is still missing a good forge.
Re: Ghostty is leaving GitHub
#739Earlier quoted context omitted.
Gitlab is pretty cool to be honest, and it’s generally underrated.
I agree, but it does have faults. Performance is woeful, and managing an on-prem instance is (literally) a full time job.
Hosting a Docker container is a full-time job? I have worked at several employers self-hosting their own instances without issues or a lot of effort. Many FOSS projects do, that definitely do not have a full-time guy for that. What are you talking about?
Re: Ghostty is leaving GitHub
#740I 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…