991–1000 of 1001 posts
The unspoken reality of github: It would be significantly better both as a product and a vehicle in our economy if it was entirely worker owned.
git is worker owned - unless the worker chooses to outsource its ownership
https://thenewstack.io/github-will-prioritize-migrating-to-a... https://news.ycombinator.com/item?id=45517173
Might explain at least a part of the issues.
I'm very interested in where ghostty ends up - I wonder if they'll follow Zig to Codeberg? It does seem like it might, in general, be a very opportune time for GitLab (or another host) to publicly step up! There seems to be a lot of chatter on X recently about wanting an entirely new GitHub usurper that doesn't look like GitHub at all, but in the short- to medium-term I expect this not to gain a huge amount of tracti…
GitLab? We use gitlab for work. Its way worse in comparison. Last week I encountered a bug where my merge request simply didn't show that I deleted a file. Apparently it's because my MR included the creation of a folder with the same name as the basename of the deleted file. Unacceptable for a code hosting platform. Other than that I miss GH Actions, a clear ui (gitlab has way too many sub-menus), a responsive ui (gi…
Do not forget: "Embrace AI or get out!" [1] https://www.businessinsider.com/github-ceo-developers-embrac...
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…
The centrality of GitHub was part of its appeal. It’s where you went to see where nearly every (obviously not all) open source project was being developed. Based on his post, the network effect was a large part of the draw and the reason he stayed despite reliability issues. A more federated set of git UIs will never capture the same feeling.
> To the "Git is distributed!" crowd: the issue isn't Git, it's the infrastructure we rely on around it: issues, PRs, Actions, etc. Yet again, I wish the prevailing SCMS were more like Fossil, where issues and forum posts, at least, are part of the repository (and everything lives in a single sqlite file). (Of course Fossil actively opposes "pull requests", separate issue)
> (Of course Fossil actively opposes "pull requests", separate issue) Not opposition, but very little incentive for the primary developers to implement the feature. Fossil's own developers happen to be the same as SQLite's developers, which doesn't accept outside contribution as a policy. It results in Fossil's features being predominantly, but not exclusively, the same features needed for SQLite and little else. Thi…