> On Feb 7, 2017, at 1:15 PM, Tino Heth <[email protected]> wrote: > >> 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. > > 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). > > 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.
>From my point of view it’s the other way around: email has been working fine. >Discourse (which I experimented with Mattt’ setup with a little) does not >recreate the same email experience (extra HTML content, code indentation >issues, etc, it’s all been pointed out in this thread but have not been >answered). Just like a language feature, it’s the proposal’s responsibility to >justify a change. > If such vague fear is enough to entrench the status quo, I'd really worry > about the impact of this mindset on future progress. > 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. > But to repeat it once more: In this case, moving to a more modern solution > keeps the old one intact. Again, either you missed issues pointed out in this thread or you are not being entirely honest with this last statement. > > - Tino > >> 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. > The reason for the original statement is that I see many similarities to > Objective-C: > 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.
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
