HackerNews中文版

我正在开发一个新的开源项目。（我的项目属于人工智能基础设施领域，已经在几个著名的基准测试中取得了 SOTA（state-of-the-art，即“当前最佳”）的成绩。）项目的核心价值不仅仅在于代码本身，而在于一种相当具体的算法方法，这种方法是经过无数次失败的尝试、实验和设计迭代才得出的。我目前面临的困境是这样的：如果我尽早开源，就能获得反馈、信任、用户，甚至可能得到贡献者。但同时，我也暴露了核心设计和算法。有了大型语言模型（LLM），将一个代码库转化为不同的实现方式比以前要容易得多。如果我保持闭源，就能更长时间地保护我的成果，但也会失去开源的主要优势：被采用、被审查、社区支持和信誉。更糟糕的是，其他人可能会构建类似的东西，并成为该领域的默认项目。我是一个几乎没有受众的新手独立开发者。如果一个大型组织或一位知名开发者看到了这个想法并发布了类似的实现，他们就能立刻获得比我几个月才能获得的更多的关注。最终，我开源我的项目却一无所获。作为一名独立开发者，你会如何处理这种情况？

查看原文

I am working on a new open-source project. (My project is in AI infrastructure. It already gets SOTA results on several well-known benchmarks.) The core value is not just the code, but a fairly specific algorithmic approach that came out of many failed attempts, experiments, and design iterations.The dilemma I am facing is this:If I open-source early, I get feedback, trust, users, and maybe contributors. But I also expose the core design and algorithm. With LLMs, turning a repo into a different implementation is much cheaper than it used to be.If I keep it closed, I protect the work for longer, but I also lose the main advantages of OSS: adoption, review, community, and credibility. Worse, someone else may still build something similar and become the default project in the space.I’m a new solo dev with almost no audience. If a large org or a well-known developer sees the idea and ships a similar implementation, they can get more attention immediately than I can get in months. And in the end I get nothing for open-sourcing my project.How would you handle this as a solo dev?

Ask HN: 独行开发者在“氛围编码”时代如何保护自己的成果？