531–540 of 1001 posts
Earlier quoted context omitted.
[flagged]
Deeper than that, but likely also that. CV-driven development, a treadmill of features nobody needs that hurts stability we do need.
Earlier quoted context omitted.
And you, my father, there on the sad height, Curse, bless, me now with your fierce tears, I pray. Do not go gentle into that good night. Rage, rage against the dying of the light. We can't really change the tide lest we be King Cnut - but we can at least take the time and effort in the things we do to fight against entropy - bring more order and durability into our lives. Or perhaps another adaptation: God, grant me…
We can; the tide changed to where it is now and can change again - and somebody will change it. People need to stop bemoaning it, and think and do something. The enshittification is an idiotic, failing, extremely short-sighted strategy. It's a huge opportunity - your competition has stopped investing in its product, fired its talent, treats its customers with utter contempt, and is managed by imbeciles. Who is a bett…
We each have to work on our areas of quality - and when everyone starts doing that, the world changes.
Reading the write-up again, this really struck me: 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. Github is really Microsoft. The above paragraph captures perfectly what it's like to work in a big company like Microsoft. When Github was a…
> 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…
Technically the issues in Fossil are part of the repository, along with the wiki, code, forum, etc. They come along with every clone and (mostly) cannot be deleted from the historical record.
Items of Fossil that are merely "alongside" instead of actually in the repository include unversioned files, chatroom content, and users and access controls. (Not an exhaustive list.)
I'm happy that raw git + mailing lists works great for the linux project, but can the rest of us all agree we actually do need issues & PRs? And that it's super painful to lose all this context when platform hopping, or when the service unilaterally decides to deplatform someone? So where are we going? Mitchell will be deciding for Ghostty. If github's current trajectory is anything to go by, everyone else will need…
tangled.org writes issues as atproto data that lives in a user's PDS which is one neat idea.
> 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)
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.
This thread discusses avenues for implementation: https://fossil-scm.org/forum/forumpost/ce238fccfd6b124d
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…
Earlier quoted context omitted.
I was late to the party: 457,207 Created at 2010-10-27T23:42:22Z. 16 years! What a wild ride. I used to use bitbucket a ton back then. I loved it. https://api.github.com/users/steveadams
I'm at 18 years and ID 1653. It took them a while to gain traction.
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…