Yes, this is really sad to see that much people in the OSS scene using nonfree ways to communicate.
At least, IRC had open-source servers and clients but in my opinion, it's too old nowadays.
At least, IRC had open-source servers and clients but in my opinion, it's too old nowadays.
A better term would be something like "Tied programmers" or "Dependent progammers". Maybe "sharecropper progammers"?
A large base of existing users, easy onboarding, and good visibility makes a big difference for many OSS projects. Using a self-hosted Git hosting system and mailing list is a lot of work—and it adds a not-insignificant barrier to entry for potential contributors. What issues exist with popular, proprietary Git and chat tools that make them unsuitable for OSS development?
What are some of the considerations you're thinking of where using a popular option is not pragmatic?
So is much of the technology behind Discourse.[1]
[1] https://discord.com/open-source (click on "OS Libraries")
as much as many projects could use a clean slate here, i dont think the burden of migranting them manually or the act of just dumping them is realistic.
Does that include Hacker News?
And the reasons are entirely understandable:
- you don't have to run your own infrastructure
- you don't have to run your own protections against fraudulent activity, DDOSes, bots etc.
- you don't have to worry about availability on any number of platforms, including mobile
And if you look at hosted services like IRCCloud, it turns out they are not that different from Slack/Discord: closed source, for full range of capabilities you need to use their apps.