3 ms·
Meh. Open source isn't magic. It can still fail just like anything else.
by bawolff 5y ago
Meh. Open source isn't magic. It can still fail just like anything else.
- chipotle_coyote 5y agoI see people downvoting this, but while it may not be artfully phrased it's absolutely true. There are countless small projects which fell by the wayside because they didn't get enough users to build a true community (e.g., "Ted," a "Rich Text Processor" that was, about 20 years ago, my favorite WYSIWYG-ish open source word processor) -- and even some relatively big name ones that were created by one company that just didn't get traction when the company stopped supporting them. Google Wave was already mentioned in the comments on this artlce and it counts; another one was the company I was at in the mid-2010s: RethinkDB. AFAIK, there's only been one minor release since the company folded and I think that release was the one that was "in progress" when the doors shut. Zulip seems like it's in a much better place to survive, taking the word of the article, with an active development community around it. (I don't think I've actually heard of Zulip after the original company was bought by Dropbox, although "whether chipotle_coyote has heard of this" is admittedly not a leading indicator of success.)
- mlinksva 5y agoThe "why" in the article doesn't rest on open source being magic: - building company without VC - 100% open source, easy to self-host, high quality import/export - building software so that it is easy to maintain and operate - substantial community of developers (100+ commits) beyond those employed by company Open source as magic seems like at most 25% of the argument, more charitably 10%.
- bawolff 5y agoI think a good point of comparison would be phabricator. It meets much of the same criteria (although much is subjective of course). Look where phabricator is now.
- mlinksva 5y agoI don't know either very well (and guess you know phabricator very well) but it seems to me the criterion that there's a big difference between the two on is the last -- significant developer community not employed by the leading entity, though it isn't _that_ strong of a point for Zulip; it isn't say PostgreSQL. That also may be the best case for the "will" in the title, though it'd of course be better to say "Why it's relatively likely Zulip will stand the test of time" or "How we've tried to build Zulip to stand the test of time" rather than "Why Zulip will stand the test of time".