Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • There was a time before programming, hacking, open source, and related communities. These things did not exist even 60 years ago. There will be a time after them, and we’ll move on to something else.
  • this could be siloed into complaints about github and pr workflows moreso than being related to FOSS. zero mention of mailing lists or patches, lol
  • We just banned gen-AI PRs, it seems to be working so far.

    Commercial dev is about results and money, and that makes AI almost impossible to resist.

    OSS has always been about process. The pleasure is in tinkering with code, collaborating with friends on a fun new idea, and helping people. I don't care about speed.

  • Close those PRs. No hesitation. No remorse.

    My project exists for the concrete purpose of helping the community get things done, not for the abstract goal of making good software. (It actually isn't very good software, to be honest.)

    If you're a real human being who needs help fixing a bug or implementing a feature, I will gladly take the time to help you. But if you're a bot that is just trying to tidy up my software in accordance with some ideal design pattern, unrelated to the specific needs of any human being, then you can just go help yourself.

    Open source projects have had gatekeeping mechanisms for decades. Remember ESR's popular (albeit exaggerated) posts about how to fit in with hacker culture? It's the same thing. There's nothing wrong with it. New contributors must prove that they know how to be a good member of any community they're trying to enter. There's no abstract ideal of openness-to-all that we must somehow all strive for. Follow the needs of the actual community that you care about. Don't feel sorry for spammers, especially non-human spammers.

  • I think the answer is straightforward. You complain that a substantial PR is no longer evidence of good faith. What is evidence? Participation in the community.

    I think mailing lists (or an equivalent) are coming back. In a big way.

  • I feel this deeply... but as an engineer at a big tech company. Over the past decade, I meticulously learned the code base and frameworks, attained readability of various programming languages, etc. I carefully wrote and reviewed code from engineers that took the time to understand what was there and how to make it better or add to it. Carefully crafting comments for feedback every so carefully to not over critique. Over the past 6 months, I have come to realize that world no longer exists. With scores of seemingly high quality code reviews from folks that don't understand what they are contributing to, it's impossible to keep up. I am also not at a place where I can say, I'm making a smaller trusted circle. Many folks in my circle are simply ramping up the quantity of code they want me to review. I simply have to rely more and more on AI to review the code and help me figure out what exactly it does. At the same time, I am also needing to generate more and more code to keep up with the expectations of those around me. We are now instructing our agents to leave comments, having the agents respond to those comments, even long threads where the agents debate technical decisions either both human author and human reviewer almost totally removed from the loop.

    We are all getting more and more removed from the profession of writing code. It's like we abstracted away all of the details of writing code and we are spending our days just sending 100 interns on project quests.

    I think some will adapt with the times and others will get burned out. This may be the end of open source as we know it, and maybe altogether...

  • There is also the fact that Maintainers simply don't need contributions any more. This I've noticed also happens at work. Everyone is maintaining their own mini stacks of things. Contribution is up cooperation is down. Why go talk to a colleague when you can talk to Claude? Change is everywhere.
  • I could not imagine the pain being being the head of a Libre/Open project nowadays.

    It used to suck when there was almost nobody contributing because it felt isolated. Worse was if your project did become popular, you would be managing loads of code AND spending loads of time managing the community than the code.

    Nowadays, you probably don't have the community to push back and converse with, just a flood of code with few people you can't actually question it with. So back to isolation but with a million lines of code.

    It feels like you would have to have a project with an direct artificial limit to increase the quality of submissions. Like, all submissions must be able to run on a 486 25Mhz and 4MB of RAM, this would keep the code small and manageable. Don't do that, but you get the idea.

Explore Birbla archives