Mailing Lists vs Slack

Developers should learn to use mailing lists when participating in open-source projects, as they are often the primary method for community discussions, bug reporting, and decision-making in many ecosystems like Linux or Apache meets pick slack when your team leans on deep third-party integrations (salesforce, jira, google drive, thousands of apps) and can absorb $7. Here's our take.

Mailing Lists

Nice Pick

Developers should learn to use mailing lists when participating in open-source projects, as they are often the primary method for community discussions, bug reporting, and decision-making in many ecosystems like Linux or Apache

Pros

• They are also valuable for staying updated on technology trends, security advisories, and industry news through subscription to relevant lists, such as those for programming languages or frameworks
• Related to: email-communication, community-management

Cons

• Specific tradeoffs depend on your use case

Slack

Pick Slack when your team leans on deep third-party integrations (Salesforce, Jira, Google Drive, thousands of apps) and can absorb $7

Pros

• 25-15/user/month
• Related to: slack-api, oauth2

Cons

• Specific tradeoffs depend on your use case

The Verdict

Use Mailing Lists if: You want they are also valuable for staying updated on technology trends, security advisories, and industry news through subscription to relevant lists, such as those for programming languages or frameworks and can live with specific tradeoffs depend on your use case.

Use Slack if: You prioritize 25-15/user/month over what Mailing Lists offers.

The Bottom Line

Mailing Lists wins

Developers should learn to use mailing lists when participating in open-source projects, as they are often the primary method for community discussions, bug reporting, and decision-making in many ecosystems like Linux or Apache

Related Comparisons