What makes using email or certain technologies uncomfortable, but using a new language or framework comfortable?
> (and I include myself)
The link with the associated comment threads we are paticipating in could have easily been an email and every comment could have been a direct reply to that email or a reply to one of the comments. Would that be more or less comfortable compared to just having this discussion on the web interface on https://news.ycombinator.com?
The only difference is that you could have to click on each comment to read the body of the message, but the tree structure would be the same as it is now.
But your comment doesn't answer my original question about level of comfort. Why is learning how to write programs, run them, and learn frameworks considered a comfortable activity, but using email is not? The former is orders of magnitude more difficult compared to the latter, so ease of use doesn't seem to be the reason.
And they all died out quickly as soon as web-based platforms stole their audience.
In my experience, any Microsoft Exchange/O365 server will most likely mangle the email server side (introducing quoted-printable encoding characters or changing the message-id field. Gmail will require that you enable insecure application access in order to use git-send-email. If you don't do that, then using git-send-email will result in a authentication failure error (which you can see if you use the --debug flag).
So this email-only workflow doesn't work with the two most popular email clients. Where do I sign up?
Clearly you don't understand the difference between a MUA and a MTA. Perhaps you should spend some time learning the difference instead of engaging in any more name calling. There's no use continuing this discussion when you outed yourself as someone who has no idea what they're talking about.
There are projects like linux that don't accept PRs on github and swear on sending patches. Obligatory Linus Rant: https://github.com/torvalds/linux/pull/17#issuecomment-56546...