Earlier quoted context omitted.
If anyone reading this is curious of their own, you can go to https://api.github.com/users/YOUR_USERNAME_HERE and fetch it. My ID is just over 10,000. Crazy to think of the journey that I've had in computing since I signed up for GitHub.
Surprised to find I am #79. I think that was down to being in a particular IRC channel when CW & co. were building it.
Ghostty is leaving GitHub
691–700 of 1001 posts
Re: Ghostty is leaving GitHub
#692I 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…
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…
Besides "That's what makes us money and pays my bills", there is no real reason to keep building github as this centralized, all-encompassing system that needs to work at global scale.
Engineering is about understanding that everything is about trade-offs, and eerything keeps pointing out to the fact that wrong choices are being made there. You can throw as many people as you want or all the MS money at it, but as long as Github "engineers" that keeps overindexing on Efficiency at the cost of Resiliency, it will feel like this pile of unusable crap
Re: Ghostty is leaving GitHub
#693Re: Ghostty is leaving GitHub
#694Re: Ghostty is leaving GitHub
#695Earlier 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 feel like MS went out of its way to make a point that GitHub and NPM would be independent orgs that no longer had to worry about making keep-the-lights-on money. It was positioned as a benevolent acquisition for the good of the development community. As so often happens, that didn't last long. Nest was originally independent. Didn't take long for it to merge with the Google Home brand. I'm sure there are countless…
If companies actually meant it then they’d sponsor these projects instead of buying them. The reason they choose to buy is so that they can make decisions about the direction of that project. If not immediately, then at least at some point in the future.
Re: Ghostty is leaving GitHub
#696Earlier quoted context omitted.
> would be independent orgs that no longer had to worry about making keep-the-lights-on money It is honestly so shameful that we keep falling for this gambit. It is nothing more than a rank "but this time is different!" Economics is what drives things. It is what drives things in households and it is what drives things in companies. Unless times are truly great or the company is truly forward-looking, promises of fre…
I remember discussions at the time where people predicted that this would certainly happen. If people “keep falling” for it, it’s not the same people. And Microsoft certainly wasn’t (and isn’t) a company you’d trust for such statements.
But you’re right that it probably wasn’t the same people that got burned by 90s Microsoft.
Re: Ghostty is leaving GitHub
#697Earlier quoted context omitted.
> "GitHub only gets better if people who give a shit stick around to make it better" This is true but misleading. Unfortunately. It is a true statement for developers working in GitHub at Microsoft. It's not a true statement for users. There is no avenue by which you make GitHub better by continuing to use it as it has been.
I do work at GitHub. I shared the above as a nuanced "yes and" to the pain that Mitchell is feeling. In the same way that Mastodon didn't replace Twitter even when Twitter went to shit, I don't believe in the various GitHub alternatives becoming a broadly-used thing. Maybe we'll end up with more GitHub-alikes like Codeberg, mabye we'll end up with some communities adopting novel forges like Tangled and Forgejo. But i…
Re: Ghostty is leaving GitHub
#698It really has been remarkable watching GitHub just crumble as an organization. There's a lot of discussion about why: the switch from being independent to being part of Microsoft, having resources pushed to Copilot instead of core service, the organization structure itself, a reliance on vibe coding, etc etc. Regardless of the reason, it's undeniable that GitHub is facing some serious issues. The unofficial status pa…
> 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.…
Re: Ghostty is leaving GitHub
#699I've never had such an obsession to a platform or an activity as this. Some might say this is unhealthy, but I admire folks who can reach this level of obsession in their craft. It's just a joy to read about for me
Re: Ghostty is leaving GitHub
#700Earlier quoted context omitted.
Tbf its free software and the quality will go up the more people are using it and contributing.
I haven’t really found that free services scale the same way. It’s hard for the “open source community” to contribute and improve the quality of bottlenecks that are only encountered by one operator. When you take OSS projects that scale well, say Linux, Postgres, Kafka, redis, etc. they either scale up (Linux) which is arguable easier, or were able to scale out because there are thousands, if not millions, that have…