Other July 2, 2026 mixed ⇧ 360 pts across 1 thread

Old-school forums vs. Discord: the community platform debate resurfaces

A post titled 'Bring back crappy forums' is resonating. The core complaint is that Discord is the wrong tool for async community building: it's built for real-time chat, so knowledge gets buried, onboarding new members is hard, and the culture rewards presence over depth. Forum-style boards, even clunky ones, produce searchable archives and slower, more considered discussion.

The counterpoint in the thread is sharp: nobody took forums away. They still exist. They're just empty because network effects pulled everyone to Discord and Reddit. The problem isn't the format, it's the cold-start problem. A forum with no users is worse than a Discord with active users, and communities migrated because the tools with momentum win regardless of which is better for the use case.

This is a recurring debate on HN but it's gaining specificity. More commenters are pointing to topic-specific forums that still thrive as evidence that the format works when the community has shared vocabulary and low turnover. The implicit question for builders is whether there's a product opportunity in async community infrastructure that's better than Discourse but less chaotic than Discord.


So what?

If you're building developer tools or products that depend on community for support and knowledge-sharing, your choice of community platform is a product decision, not an administrative one. Discord scales poorly for technical documentation and async problem-solving. A well-run forum or structured async tool can be a genuine moat because it compounds knowledge over time in ways Discord never does.

Read these