<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>On Tue, Feb 7, 2017 at 1:15 PM, Tino Heth via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br></div></div></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span class=""><div><blockquote type="cite"><div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">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.</span></div></blockquote></div><br></span><div><div>I have full comprehension for those who want to keep their email workflow as it is, but as it has been pointed out many times before: Discourse has support for that… (and it's a little bit annoying to see many fans of email ignoring this fact in their argumentation over and over).</div></div></div></blockquote><div><br></div><div>This isn't really fair; while Discourse does have email support, it is not perfect, and would not be a "first-class" experience for those who are inclined to continue using mail clients. We <a href="http://discourse.natecook.com/t/an-evaluation-of-mailing-list-mode/3053">tested</a> <a href="http://discourse.natecook.com/t/add-last-where-and-lastindex-where-methods-to-collections/3058">this</a> on Nate's demo site. As some have pointed out, the emails are less "raw" in that they have some Discourse UI on top of the actual content, and more importantly, inline replies do not work very well (unless someone wants to drastically improve the <a href="https://github.com/discourse/discourse_email_parser">email parser</a>).</div><div><br></div><div>Personally I believe that the benefits vastly outweigh these drawbacks, but other than enumerating both (as we have already done in this thread and several prior), I'm not sure what is left for the community to discuss here. Final evaluation of the benefits and drawbacks can be left to the internal team responsible for shepherding the community.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><br></div><div>So there are clear benefits associated with a switch, whereas the disadvantages are more or less hypothetical and might as well be proven wrong by reality.</div><div>If such vague fear is enough to entrench the status quo, I'd really worry about the impact of this mindset on future progress.</div></div><div><br></div><div>Telegraph and morse code are much more mature than even email, and more reliable than this whole internet-thing, and there are marked pieces of clay that exist for thousands of years and might still be readable when all our modern digital data is forgotten, so progress is definitely not always improvement in every aspect.</div><div>But to repeat it once more: In this case, moving to a more modern solution keeps the old one intact.</div><div><br></div><div>- Tino</div><div><br></div><div><span class=""><blockquote type="cite">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.</blockquote></span>The reason for the original statement is that I see many similarities to Objective-C:</div><div>I know several people who oppose Swift very strongly, although the mature and reliable Objective-C with its customised compilers and lower requirements happily coexists with its successor.</div></div><br>______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br></blockquote></div><br></div></div>