<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>I think the arguments about whether Swift is young doesn't really help resolve the argument here. Even an old project would benefit from the best setup to run the community. That to me is what we are discussing here. Let's leave sensational arguments out of it, if we can. I'm not motivated so much by what is hip, but what will empower the community the most.</div><div><br>On Feb 7, 2017, at 9:00 AM, Daniel Duan via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Very sensational arguments.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I agree with email is and Swift is young. Not sure that's a real reason to ditch email, however 😀. In fact, I could say *because* email is so old, everything about it has become mature and reliable. Besides great, customized clients, it's also a lower requirement for participants. Believe it or not, not everyone in the world can afford the device and data plan for a JavaScript-rich web front end (I'm aware of the mobile apps). I remember only being able to buy an iPod Touch myself when it came out. I *would* be able to participate SE if it existed back then. Because email is so old and work well in offline environment.</div><div><br></div><div>On Feb 7, 2017, at 4:08 AM, Tino Heth <<a href="mailto:2th@gmx.de">2th@gmx.de</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><div><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I’d encourage those who want web forums to give Mail.app a try. It does a remarkable job of keeping emails threaded.</span></div></blockquote></div>That doesn't read like we are using the same Mail.app… it's not failing on a regular basis for me, but it's far away from being remarkable (at least not remarkably good).<div class=""><br class=""></div><div class="">Sticking with Email feels terribly behind the times, and considering Swift being such a young language, that imho is really odd.</div><div class="">Email is old and trusted, but the emphasis is on old: The whole protocol has big flaws which no one anticipated in the early days, which have never been fixed, and which most likely won't be fixed ever.</div><div class="">Discourse on the other hand may have some features that could have a tiny negative impact for those who prefer to keep things as they have been in the eighties, but it is not a huge network of servers and clients governed by several billion different parties which makes progress impossible.</div><div class="">It's a single software fully controlled by whoever sets it up — and you know what: It's even open source!</div><div class="">So every programmer here has the ability to solve all the issues that have been brought up as an argument to stick with mailing lists (and as it happens to be that I am a programmer, that gives me a great feeling of empowerment, whereas the legacy of email leaves me powerless).</div><div class=""><br class=""></div><div class=""><br class=""></div></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>