Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ghostty is leaving GitHub

mitchellh.com

Post reply on HN
Print view View original

861–870 of 1001 posts

Re: Ghostty is leaving GitHub

#861

Post by golddust-gecko »

idan wrote: post #96
mitchellh wrote: post #26

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…

> "GitHub only gets better if people who give a shit stick around to make it better"

At best that's half of the equation. You also have to continually hire new people who give a shit, and you have to do that within the context of Microsoft.

Given the rot already evident, there really isn't any incentive for people who care to join. They would have to care more than the organization does about the product, and there would have to be many of them.

Once product in large companies get to this point, there's no real way back. Quality will max out at the minimum required to retain the revenue. And if that fails for too long, it'll be put in product hospice.

Re: Ghostty is leaving GitHub

#862

Post by nextaccountic »

samuell wrote: post #831
nextaccountic wrote: post #52

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

There is also epiq, which is a bit more bleeding edge but has a more powerful UI story, being a TUI app, providing an issue board in the terminal: https://github.com/ljtn/epiq

Oh that's interesting!

Does it have bidirectional tracking with Github? (if I create or comment on an issue in Github it will be reflected on epiq, and if I create on epiq, some bot will post it to Github). For me this is the key feature.

Also

> The system is designed to assure robustness and uses a number of techniques and design patterns to avoid merge conflicts.

I think the docs should describe this in detail.

Anyway maybe ask him to post this to HN some day!

Re: Ghostty is leaving GitHub

#863

Post by nextaccountic »

Zambyte wrote: post #419
senko wrote: post #92

Earlier quoted context omitted.

Maybe Mitchell will pull a Linus and, out of frustration, take a weekend off to write the distributed infrastructure for issues, PRs, actions, etc. around git.

https://radicle.dev/

Are radicle issues and PRs stored in the Git repository itself, or is it out of band like other forges, with just federation on top?

Re: Ghostty is leaving GitHub

#864

Post by nashadelic »

nine_k wrote: post #575
idan wrote: post #415

Earlier quoted context omitted.

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…

Speaking of a "year of Linux on desktop", it's mostly not happening because the desktop lock-in has largely eased. I of course love my Linux desktop, but I use relatively few native applications, and every one of them is multiplatform now. Windows desktop becomes less and less relevant in its own way, by degradation of experience, and by being replaced with consoles and the Steam Deck. Same may happen to GitHub. CI/C…

Whats funny is that nearly every major desktop app and feature has come out on macOS first and windows has nearly always been an after thought

Re: Ghostty is leaving GitHub

#865

Post by andruby »

ngrilly wrote: post #698
_doctor_love wrote: post #138

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

There might be a few (debatable) counter-examples: 37 signals, balsamiq, zoho?

Afaik they never took any (serious) VC money.

Re: Ghostty is leaving GitHub

#866

Post by jolaflow »

nextaccountic wrote: post #862
samuell wrote: post #831

Earlier quoted context omitted.

There is also epiq, which is a bit more bleeding edge but has a more powerful UI story, being a TUI app, providing an issue board in the terminal: https://github.com/ljtn/epiq

Oh that's interesting! Does it have bidirectional tracking with Github? (if I create or comment on an issue in Github it will be reflected on epiq, and if I create on epiq, some bot will post it to Github). For me this is the key feature. Also > The system is designed to assure robustness and uses a number of techniques and design patterns to avoid merge conflicts. I think the docs should describe this in detail. Any…

Hey! Creator of Epiq here. Epiq is platform agnostic mening that it is doing its own thing and does not connect to github issues. Epiq maintains its own board definition as an immutable (append only) event log, which is synchronized using git.

An integration layer with github issues or other platforms is definitely not unthinkable.

V1 is about to be released in the coming days.

Re: Ghostty is leaving GitHub

#867

Post by flexagoon »

Andrex wrote: post #853
sho_hn wrote: post #292

Earlier quoted context omitted.

> Github has always been non-free software hosted by someone else, and run according to its owners' rules and for its owners' benefit, not ultimately the end user. This was true in 2008 and it's true today. Yup. At KDE we never seriously considered GitHub. We always built our own git infra, and eventually landed on GitLab, after banding together with Gnome and a (generous and forthcoming) GitLab to convince them to m…

Seeing KDE and Gnome come together isn't exactly uncommon but it still warms my heart reading about it.

Unlike their fanbases, KDE and Gnome teams collaborate all the time

...until it comes to bikeshedding new standards

Re: Ghostty is leaving GitHub

#868

Post by jitl »

toastal wrote: post #289
mamcx wrote: post #149

Earlier quoted context omitted.

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.

Xit has a better “take” on Git. Pijul & Darcs still have better fundamentals.

worse is better

pujil's patch alebgra is sick but the whole system implementation is so complex my guy is still toiling away on it, unfinished, after half a decade

Re: Ghostty is leaving GitHub

#869

Post by gsaslis »

nextaccountic wrote: post #863
Zambyte wrote: post #419

Earlier quoted context omitted.

https://radicle.dev/

Are radicle issues and PRs stored in the Git repository itself, or is it out of band like other forges, with just federation on top?

yes, they're stored in git itself. See https://radicle.dev/guides/protocol#collaborative-objects

Re: Ghostty is leaving GitHub

#870

Post by mplanchard »

poidos wrote: post #596
eiiot wrote: post #172

This seems like a great opportunity for new platforms who are rethinking the OSS space to finally gain the traction they need to be effective. For a collaborative platform, quantity is key, and I am hopeful that someone who is interested in advancing the software space will become the new go-to. This isn't to say that GitHub hasn't been innovating, but at least from my perspective, the way we've used git for the past…

Love sourcehut and want to see them succeed, but their build service (despite having some very cool ideas like allowing you to SSH into your build container) is pretty barebones / lacking compared to GH/GitHub actions. You either get no task parallelism (all your tasks are in one manifest) or you get up to N=4 parallelism (you have four manifests). As far as I can tell, you can’t specify job dependencies beyond just…

OTOH, the nice thing about a minimalist build system is it forces you to solve these problems yourself, in a way that’s broadly compatible with any provider: for me, nix builds, cache with cachix, and use gnu parallel for running concurrent jobs.

Means that my CI pipeline can be ~instantly moved to any provider, or a box that I own, or whatever.

Post reply on HN