IssueRaiser

> Do you still not believe most email is formatted at 78 characters?

> Do you still not believe most email is formatted at 78 characters? Really? I've stated my reasoning, you haven't refuted that or explained any alternative. You've essentially stated that you don't know either (you haven't really read your users' emails, have you?), and I have explained why it doesn't matter anyhow, so I don't see any need to refute anything. > No, we've already discussed why they're worse and you haven't even attempted to rebut it. No, we haven't. > they not representative of common email use cases (a) Yes, they are - are you maybe confusing use cases (what it's for) with workflows (how it's applied to that use case)? (b) How exactly is that even relevant? Because linux kernel developers are not representative of email users, it's fine to break email in a way that doesn't work for linux kernel developers? I mean, kinda my whole initial point was that exactly that is terrible engineering. > for the same reasons I have mentioned earlier Actually, you haven't. > which you have not refuted in any way. As such, there is little to refute. > They do, but displaying email is a critical part of email clients. so? > Another part of email list etiquette: Part of that is that you sincerely try to understand the other side's position, don't quote out of context, don't misrepresent, don't just repeat talking points without actually considering and addressing the other side's arguments, question your own implicit assumptions, ... - that avoids the frustration that you are seeing there.

Posted by zAy0LfpBZLC8mAC on Jul 7, 2014, 7:00 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments

hackernews (Sysadmin)

> Do you still not believe most email is formatted at 78 characters?

zAy0LfpBZLC8mACJul 7, 2014, 7:00 PM

> Do you still not believe most email is formatted at 78 characters? Really? I've stated my reasoning, you haven't refuted that or explained any alternative. You've essentially stated that you don't know either (you haven't really read your users' emails, have you?), and I have explained why it doesn't matter anyhow, so I don't see any need to refute anything. > No, we've already discussed why they're worse and you haven't even attempted to rebut it. No, we haven't. > they not representative of common email use cases (a) Yes, they are - are you maybe confusing use cases (what it's for) with workflows (how it's applied to that use case)? (b) How exactly is that even relevant? Because linux kernel developers are not representative of email users, it's fine to break email in a way that doesn't work for linux kernel developers? I mean, kinda my whole initial point was that exactly that is terrible engineering. > for the same reasons I have mentioned earlier Actually, you haven't. > which you have not refuted in any way. As such, there is little to refute. > They do, but displaying email is a critical part of email clients. so? > Another part of email list etiquette: Part of that is that you sincerely try to understand the other side's position, don't quote out of context, don't misrepresent, don't just repeat talking points without actually considering and addressing the other side's arguments, question your own implicit assumptions, ... - that avoids the frustration that you are seeing there.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue