901–910 of 1001 posts
Earlier quoted context omitted.
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…
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.
Earlier quoted context omitted.
This isn't a surprise at all. I saw the exact same thing at Meta. The incentives are so strong to improve your individual performance that it's hard to resist, literally hundreds of thousands of dollars at stake. Now with the fear of constant layoffs at Microsoft and Meta too, it's even more critical for individual engineers to optimize their performance review or you might lose your job. Sadly this is hard to line u…
Maybe I'm naïve, but it seems like the people who keep their eye on the ball and really try to make a great product are the ones who win out in the long run. If you optimize for performance reviews, you'll make a lot of money, yeah. But you'll eventually find yourself overemployed and incapable of keeping up with that gambit anymore. Or, you'll find yourself doing something you never wanted to do. In extreme cases, i…
Earlier quoted context omitted.
git-bug is great but it doesn't handle PRs nor does it have a method for users without commit rights to submit bugs to the project. I know they're working on the latter (something with the web UI?) but until then you still need some kind of public infra for issue management if you want the general public to be able to submit issues. I use it for my project[0] to keep issues centralized with the repo, but I still use…
For me the main issue with git-bug is that they are not dogfooding it. However , it's also one of the few projects that is actually trying to solve the core problem, rather than skirting around it. (well I now learned of radicle in this thread and they seem to store issues in git and even have PR support I think)
This is incorrect.
$ git remote get-url origin
ssh://git@github.com/git-bug/git-bug.git
$ for n in bugs identities; do echo "${n} on the remote: " $(git ls-remote origin "refs/${n}/\*" | wc -l); done
bugs on the remote: 453
identities on the remote: 311
That said, yes, GitHub is still our source of truth, as our web application does not currently support "guest" access, and there are other platform features that our community uses that we do not currently have support for (e.g. discussions and pull requests). Big changes to the web ui are coming soon, which will help to unlock the ability to do these things.
I've also been in talks with the Radicle team about possible collaboration.
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…
> I'm sure folks will make fun of me for this To be honest, the blog post is quite a lot of self-indulgent waffle. But I forgive you for that, "each to their own", as they say. What I won't forgive you for is writing such a long blog post and then completely missing the bottom-line. Do not write "I'll share more details about where the Ghostty project will be moving to in the coming months" . If you're going to make…
Ghostty might be an open source and free product, but that doesn't mean that Mitchell in particular, that works on it, treats it any differently to how a for-profit company would treat its own software.
If you're using a SAAS that offers a product to both companies and individuals with the same feature set, and it's uptime is anything less three-nines, it's not fit for purpose.
Frankly, I'm amazed companies aren't walking away and giving the same reasons.
Earlier quoted context omitted.
This isn't a surprise at all. I saw the exact same thing at Meta. The incentives are so strong to improve your individual performance that it's hard to resist, literally hundreds of thousands of dollars at stake. Now with the fear of constant layoffs at Microsoft and Meta too, it's even more critical for individual engineers to optimize their performance review or you might lose your job. Sadly this is hard to line u…
Maybe I'm naïve, but it seems like the people who keep their eye on the ball and really try to make a great product are the ones who win out in the long run. If you optimize for performance reviews, you'll make a lot of money, yeah. But you'll eventually find yourself overemployed and incapable of keeping up with that gambit anymore. Or, you'll find yourself doing something you never wanted to do. In extreme cases, i…
Those "overemployed" people are your bosses, indeed unable to keep up, steering you into the situation of "those people at Palantir".
When things spiral downward, telling yourself how you're "relatively fine still" with blinders on short-term, "works" just up to hitting solid ground.
> 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…
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.
It was born out of frustration and does just that. It is about to go v1 within days.