[komali2]

I was in this world for like 8 years but switched to Thunderbird after one too many emails didn't send because I missed some notification or something in mu4e, and too many emails weren't rendering well in Emacs, and etc little problems that cropped up. I needed my email to Just Work, not be another aspect of my procrastination machi- sorry I mean, my IDE.

[ubermonkey]

The need for email to Just Work is one reason I've never let emacs anywhere NEAR my email flow.

Everything in emacs becomes a Project.

[imiric]

The nice thing is that once things are setup in Emacs, they usually work without much maintenance or surprises for years to come. How many times have mainstream email clients changed UIs and featuresets in the last 10 years? How many of them do you expect to still exist 10 years from now?

Another benefit is that using standard mailbox formats and separate tools allows you to configure, replace, and integrate any part of the setup. With traditional clients you're locked into whatever they support and allow you to configure.

[ubermonkey]

And yet: my mail flow on my Mac, using the native client, is effectively unchanged for 20 years. I've changed back-ends, sure, but that's a different thing.

And I never had to hack anything together.

[imiric]

Whatever works for you, but I don't believe that your mail flow on the Mac is "effectively unchanged for 20 years".

Wikipedia lists many UI and functionality changes over the years for the Mail app.[1] As recently as this year, people are upset about changes in the Mail app in recent versions.[2]

[1]: https://en.wikipedia.org/wiki/Apple_Mail

[2]: https://www.macrumors.com/how-to/get-old-apple-mail-back-ios...

[ubermonkey]

Kinda peak HN crap to suggest I don't know how my own mail flow has worked.

Has the interface in Mail evolved since the early 2000s? Yes.

Does that constitute a material change, or even an adjustment, on my part? No.

Did I ever have to hack anything together to make this happen so smoothly for so long? Also no. ;)