被 r/java 封禁
Getting Banned from r/java

原始链接: https://sjhannah.com/blog/2026/05/30/getting-banned-from-r-java/

作者因分享一个用 AI 构建的 Swing WebView 组件而违反了新的禁止 AI 规则,被 r/java 永久封禁。尽管并不因封禁而愤怒,但这件事揭示了自 2025 年底 AI 超越人类编码能力以来,AI 改变软件开发所引发的深层挣扎。他们认为手写代码如今主要用于娱乐或学习;对于真实项目,AI 对效率和质量至关重要。他们承认情感上的损失:辛苦获得的技能感到被贬值,身份认同受到冲击,而且新人瞬间获得更强大能力似乎不公平。他们理解禁止 AI 的空间是为保护技艺与社区所做的尝试,但认为由于 AI 辅助代码日益普遍,这些尝试最终是徒劳的。回顾自 1998 年以来的 Java,他们感到悲伤:将不再手写代码,而是引导和审查 AI 代理——获得生产力,却失去技艺以及对 r/java 等社区的参与。

一个Hacker News讨论围绕一名开发者因在新“禁止AI”规则下分享含AI的软件而被r/java封禁展开。评论者争论不用AI手写代码是否已变得低效。支持AI的声音认为模型能提高速度与生产力,有时在bug、安全和性能检查上优于人类,拒绝任何AI审查是不可辩护的。怀疑者反驳AI代码往往需要大量审查,可能缺乏系统层面的一致性,正确性、可维护性和 craftsmanship 仍重要;AI是工具,不是理解的替代品。其他人将开发者分为结果导向与 craftsmanship 导向,并讨论结对编程、版主权力动态以及严格Reddit封禁的问题。有人引用Linus Torvalds使用AI。总体而言,该帖反映两极化但细致的观点:AI可提升生产力和审查能力,但人类判断仍不可或缺,围绕AI的平台 moderation 具有争议性。
相关文章

原文

I got banned from r/java today for posting a Swing WebView component that I made. A lifetime ban.

The offence was that I had broken rule #9, which I hadn’t noticed, and was new since the last time I posted there. This rule forbids sharing any software that involves AI at all.

I used AI extensively to develop this library, so, based on the wording of the rule, I definitely broke the rules, and the consequences are a lifetime ban.

This makes me feel a lot of things. I’m not so upset by the banning. I don’t think I’ll notice inclusion or exclusion from that forum, but it brings to the surface some of the internal struggles that I’ve been feeling since late 2025 regarding changes to the software development process. Late 2025 is basically when AI became better at coding than humans — and I suppose it isn’t a coincidence that that is approximately when r/java adopted their No AI policy.

In 2026, if you are still writing code “by hand” without AI assistance, then either you haven’t tried using AI, or you are just coding for fun — without any desire to be productive. However, if you have a goal in mind to build something, then you would be foolish to do it “by hand”.

Don’t get me wrong, I do miss the high of coding — spewing out algorithms line by line, riding the flow state through a day without any concern, or notice for the time that passes. It is fun, and exhilarating, but the only compelling reason to code that way anymore is for personal enjoyment, or to exercise your “coding muscles”. Those are valid reasons, but you have to weigh them against the vision in your head of the finished product that you want to realize. Insisting on hand-coding a project for these reasons is akin to choosing a shovel over an excavator because you want to build muscles and get a farmer’s tan. If you need to dig the foundation for a house, you should use the excavator — especially if you’re getting paid to do it. If you want to exercise your shovelling skills, then you can do that on your own time.

If I write code without AI anymore at all, it will be just for my own indulgence and learning. I would never actually ship any code anymore without using AI to review it, or to help write it, because that would be inefficient, wasteful, and produce a worse result.

But I understand the sentiment that leads to No-AI policies like this. AI is better at coding than we are now — after we’ve spent our adult lives building up these coding skills. Our identity is built around all of the coding skills we’ve developed, and now, all of a sudden, some guy off the street can type a prompt into AI, and produce better code than we could. It’s not fair. All of the time we spent practicing, learning, and honing our skills; hard-fought lessons that left us bloodied and bruised. Now a 12-year-old instantly has all of the same skills — nay better skills — without any work, or discipline. It’s not fair.

So, let’s try to level the playing field by making safe spaces where AI is not welcome. Maybe then we will be free to practice our hand-coding skills with others who appreciate the importance of hard work, persistence, and discipline — where my lived experience has value.

Unfortunately, that’s a fool’s errand. The genie is out of the bottle. Every piece of software that matters, going forward, will be coded by an agent, with humans guiding them, and reviewing them. Projects like the OpenJDK almost certainly already have substantial amounts of AI-assisted code. So a strict No-AI policy in a sub like /r/java, if we follow the letter of the rule, should disallow sharing even links to OpenJDK. But that’s absurd.

At some point in the future, I’m sure this irony will become too obvious to ignore and they’ll need to move the goal posts.

For me, it’s a little bit sad. I’ve been developing in Java since 1998, and I plan to continue developing in Java for the foreseeable future, but it has changed. I don’t think I’ll ever be writing it by hand anymore. I’ll be getting agents to do it for me, and guiding and reviewing them. There is something lost in that, and more than just my ability to participate in /r/java.

联系我们 contact @ memedata.com