Live data from Hacker News

Ghostty is leaving GitHub

mitchellh.com

761–770 of 1001 posts

Re: Ghostty is leaving GitHub

#761

Earlier quoted context omitted.

Honestly the arrogance of their workers are truly astounding. It also tracks that someone with little software experience would become GitHub's staff research engineer. Truly a massive signal that we can't let these companies lead the direction of tech in our country.

The state of HN truly has fallen if people are questioning Maggie Appleton's credentials. Besides, she's working on GitHub Next , not the core product. Sheesh.

By credentials you mean, and I mean no offence, that she is an established artist and has a great personal website?

She is internet famous, sure, but she still has to prove if her ideas on how to evolve GitHub are the right one.

Re: Ghostty is leaving GitHub

#762
post #720

Earlier quoted context omitted.

I agree, but it does have faults. Performance is woeful, and managing an on-prem instance is (literally) a full time job.

> 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?

Hundreds or 10k+ users?

I imagine requirements and integrations may differ a lot. I have seen many incidents with a large instance.

Re: Ghostty is leaving GitHub

#763
post #277

>It’s not a fun place for me to be anymore. I want to be there but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software. Has anyone else shared this sentiment? If so Redmond needs to lean in hard. this is an absolute killing blow for Microsoft if it gains real traction. You made developers your cornerstone eigh…

> Youve lost the OS, and the server realm. Lose the developers, and youre on your way to becoming the Xerox of the 21st century. This is a very HN take. MS is terrible or at best "second tier" on everything they do including gaming, they also lost the mobile race, they're very likely going to lose the AI race, but they'll still hold hostage of the vast swathes of average white collar workers with Office, people that…

Is this even an issue these days ? I thought GSuite was good enough for most office work for a very long time now ?

Re: Ghostty is leaving GitHub

#764
post #149
post #22

During 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.

Does it do anything that GitLab does not?

With what I heard about GitHub Actions, the GitLab CI pipelines should be much better.

Not that I haven’t shot myself in the foot with GitLab pipelines on numerous occasions.

Re: Ghostty is leaving GitHub

#766

Earlier quoted context omitted.

I have had my eye on these technologies for a while. Embedding the issue tracker and such in your git repo. Every day these make more and more sense. - https://gitsocial.org/ - https://radicle.dev/ - https://github.com/git-bug/git-bug

I made the decision to leave Github a couple months ago when I retired and started heavily working on personal projects. I like the idea of radicle and used it for a while, but it's complicated to set up and maintain if you want to run your own seed node and pin your personal projects. What I ended up with is a version of a static forge - Charm's soft-serve to host the repos and a forked version of the pico.sh pgit s…

I would agree with everything you say, but why not both?

We are actually facing 2 distinct problems:

- Github is a centralized, controlled git hosting, identity, collaboration platform.

- Bots are attacking any public facing interface.

So maybe the solution is:

- to keep a Radicle node private/behind fences to lower the maintenance/security burden, with eventually access to selected collaborators.

- publish the repos with a static site generator like pgit

Re: Ghostty is leaving GitHub

#767

> 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…

It's definitely time to turn these loose web features into a real program. I don't understand the desire to clone github as a website. It's demonstrably 10,000x more work to maintain github.com than a "github" command.

Re: Ghostty is leaving GitHub

#768
post #96

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…

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…

Just an observation: The different approaches mentioned in the replies to this post seem to all neatly fall into one of the three types of individual response (exit, voice, loyalty) there are to any sort of decline in/of firms and organizations of any kind within Albert O. Hirschman's well-known economic framework, originally laid out in Exit, Voice, and Loyalty: Responses to Decline in Firms, Organizations, and States (1970).

Personally, I find "loyalty" perhaps the most fascinating one of those, being "irrational" for the individual almost by definition but sometimes, for example, proving out to be the only "glue" holding an organization together through a period of incurable-looking decline followed by an eventual recovery (in the lucky cases).

Re: Ghostty is leaving GitHub

#769
post #195

Earlier quoted context omitted.

This is my darkly optimistic take on enshittification: Companies know how to make good product, but if they don't have "new and shiny" to impress us anymore, then their only alternative is to make things worse so they can heel turn and then make things "better" by unmaking all of the worse things they did. They can also milk their customers coming and going in the process. It's not "enshittify or lose", its just raw…

When is the "get better" step? I've only ever seen two things happen mid- or post-enshittification: 1. The company builds a moat and just remains shit. 2. New entrants either displace the company entirely (most likely) or competition slows the enshittification process (distant second) or reverses it (almost never). It's not clear to me why "get shitty" is a necessary step to this. What part of GitHub's executives' gr…

> What part of GitHub's executives' grand plan is "have a barely-functional service

What about lock-in, being a monopoly? Why wouldn’t you maximize on saving costs? Sure some people leave, but the majority is not going anywhere. And if the platform dies they’ve made more money than to keep it alive.

Re: Ghostty is leaving GitHub

#770

Earlier quoted context omitted.

Honestly the arrogance of their workers are truly astounding. It also tracks that someone with little software experience would become GitHub's staff research engineer. Truly a massive signal that we can't let these companies lead the direction of tech in our country.

The state of HN truly has fallen if people are questioning Maggie Appleton's credentials. Besides, she's working on GitHub Next , not the core product. Sheesh.

What credentials related to software engineering? Please expand and do not post nebulous comments like these.
Post reply on HN