efronlicht

1. Negativity moves humanity forward all the time. Have you read the American declaration of independence lately? It is mostly an enormous list of complaints about the British government. As citizens we have both the right and the duty to call out abuses when we see them. (The article's title is a reference to Charles Sumner's 1856 speech "The Crime against Kansas", a historic callout post if there ever was one).

2. I provide direct, actionable solutions. Saying I have to submit the PR is just moving the goalposts.

3. I have no idea if they know how to write performant code: all I know is that they don't.

4. The fact that GitHub was good for ten years and is now hot garbage is exactly my point. It should make you less tolerant of its decay, not more.

5. It is entirely within GitHub's power to rate limit the bots to protect their actual users. They choose not to do so, because they care about "ai" more than customers.

The same way that an employee might only use GitHub on behalf of their employer. It's not mysterious or complicated. If my client brings me in to help on a software project that's already hosted on GitHub, that's what I have to use. So I use GitHub pretty much every workday, because I want to get paid. This is part of the problem: GitHub remains the default despite the fact that it is no good. Hence me writing the article, to try and change that.

Before I went independent I used GitHub for a bunch of different employers, so I've watched it's decline over the last decade from the front row.

My clients are the ones paying for GitHub enterprise, in this case. Depending on the context I'll either use my personal account or an account under their organization, etc. Usually I don't have admin permissions (rightfully!), sometimes I do.

I have used pretty much every corner of GitHub in pretty much every possible context for well over a decade. I'm sure you could find something I haven't touched, but you'd have to think pretty hard. I thought that would be obvious from the fact I talked about things like SLAs and GitHub actions, but I guess I should have been clearer.

Author here. I am not a free GitHub customer. The only times I use GitHub are when my consulting clients do, who are by and large GitHub enterprise customers. It is not entitlement to complain about a company that you pay money for a service failing to provide that service by the terms of their own service lifetime agreement, something I point out repeatedly.

Author here. For those who don't care for the color scheme, my site has - a light theme: https://eblog.fly.dev/githubbad-light.html - a plain theme: https://eblog.fly.dev/githubbad-plain.html, added as part of the same update where I submitted this article. Both of those are available as PDFs as well (replace .html with .pdf).

And of course you can use reader mode in your favorite browser.

People keep saying "if you don't need a framework, how are you supposed to do backend in Go?"

So I figured I'd try and answer! This is the article that's taken the most time and sweat yet. Part 2 is already up, and part 3 should be done within the week. Hope this is helpful!