我们不需要更多应用。我们需要更好的开源。
We don't need more apps, we need better open source

原始链接: https://jordankrueger.com/blog/better-open-source-not-more-apps/

AI辅助编程正在改变谁能够构建软件,但它的能量也应改善人们已经依赖的开源工具。作者认为,开源软件往往很好,但难以运行:安装复杂、升级脆弱、资源占用高、错误信息差,以及系统管理需求,这些都会把组织推向大型科技公司。他们提出四个有用的周末项目:加快常见操作、将安装简化为一个带合理默认值的命令、通过管理界面、安全升级、备份和清晰错误信息让日常运维更轻松,以及降低资源占用,使工具能在廉价服务器或旧硬件上运行。这能帮助数百万用户,支持非营利组织的数据所有权,并减轻维护者倦怠。AI可帮助性能分析、测试、安装器、错误信息和文档,但贡献者必须尊重:先使用工具、咨询维护者、提供测量结果、保持改动小且经过测试、披露AI使用、修复破坏,并接受“不”。若被拒绝,可改进下游安装器或指南。选择一个工具,与维护者一起修复其最恼人的安装或运行问题,然后分享。

讨论聚焦于AI应改进现有开源项目,还是让人们自己构建应用。维护者报告被针对假设性、轻微或低价值问题的AI生成PR淹没,导致倦怠、更严格的贡献政策,有时甚至放弃维护。部分贡献者为AI辅助修复真实问题辩护,其他人则警告垃圾内容、简历刷量和安全风险。另一主题认为AI让定制软件便宜且实用,减少对共享应用的依赖,但批评者指出重复重新实现、许可问题、支持缺口和质量担忧。总体而言,参与者对AI影响存在分歧:它降低了软件创作门槛,但给开源规范、维护者能力和社区协作带来压力。
相关文章

原文

Every day, a dozen people post a new app they built with AI over a weekend: a habit tracker, a to-do list, another note-taking app. I’m glad! More people building things is one of the best parts of this moment.

But far less of that energy goes into the open source software we already rely on.

People call this new way of building “vibecoding.” I hate the name; it makes a real shift in who gets to write software sound like a joke. I’ll call it AI-assisted coding, and I think it could aim somewhere more useful.

Free and open source software already does most of what my clients and I need. What it often can’t do is run well on a cheap server, install in one step, or stay up without forum threads at 11pm.

Where I’m coming from

I self-host a lot of my own stuff, and I help progressive nonprofits with their tech for a living. I run a Matrix server (Synapse, Element and a moderation bot) for a community with thousands of users. I also run apps on Coolify and Hetzner, keep my paperwork in Paperless-ngx, and own a Mac Mini that’s always one download from a full disk.

The software is usually great. Running it is the hard part. Install guides assume you know five other tools. Upgrades break things. Apps eat 4GB of RAM to serve a handful of people. Error messages tell you nothing.

My nonprofit clients would love to leave Big Tech for privacy, cost and owning their data. But the open source option usually needs a part-time sysadmin they don’t have, so they pay for the corporate tool.

Four jobs worth your weekend

  1. Make it faster. uv took a job Python developers do every day, installing packages, and made it 8 to 10 times faster than pip in its makers’ benchmarks (up to 115 times with a warm cache). Find the slow part of something people already use, measure it, fix it.
  2. Make it easy to install. Too many apps need a database, a cache, a background worker, a reverse proxy and a long config file before you see a login screen. Aim for one command, sensible defaults and a setup that works the first time on a cheap server.
  3. Make it friendly to run. Installing happens once; running it happens every day after. Give it a simple admin screen, safe upgrades, built-in backups, errors that say what to do next, and an easy, secure way to manage logins and add admins.
  4. Make it lighter. If a tool runs happily on a $5 server, an old laptop or a Raspberry Pi, far more people can use it. Lighter software costs less to run and uses less energy.

Why this matters

A new to-do app usually helps the few people who find it. Making a tool millions already use 20% lighter helps all of them, every day.

This is also the work that slides when maintainers are tired, and many are unpaid volunteers. We saw the risk in 2024. Someone spent years earning the trust of the worn-out solo maintainer of xz, a compression tool inside most Linux systems, then slipped a backdoor into it.

I think this unglamorous work suits AI well: profiling slow code, writing tests that make big changes safe, testing installers, rewriting cryptic errors, writing the missing docs. It takes patience more than brilliance, plus a person who checks every line.

It matters politically too. If organizations are going to own their data instead of renting it from a few giant companies, open source has to be something a 20-person nonprofit can run. I want AI’s gains shared widely. Better public tools that anyone can use, change and share are one way to get there.

Don’t be a jerk about it

Maintainers have already seen the wrong way. The curl project ended its bug bounty in January 2026 after a flood of fake, AI-generated security reports. By April, its lead developer wrote that the fakes were mostly gone and almost every report used AI, most of them very good. The new problem is volume. Even good work can bury a maintainer. So:

  • Use the thing first and find what actually hurts.
  • Talk to maintainers before writing code. Nobody wants a surprise 4,000-line pull request.
  • Bring numbers. “Startup went from 40 seconds to 4, here’s how I measured it” beats “faster.”
  • Keep changes small and tested.
  • Say you used AI, and own the result. Stick around to fix what breaks.
  • If they say no, help downstream with a better installer or setup guide, and keep it current.

Pick one open source tool you use. Find the most annoying thing about installing or running it. Spend a weekend fixing it, with the people who maintain it. Then tell me about it.


Sources

联系我们 contact @ memedata.com