Re:Help me kill IMAP and Exchange in a single blow
by pornel on Sunday August 07, 2011 @11:23AM
(#2856776)
We don't have current mail protocols because nobody was able to come up with anything better — we have them, because we need interoperability and it's nearly impossible to migrate all servers and clients to a new protocol.
I think the best bet is to do to "IMAP5" in the same way HTML5 has been done:
• keep basic functionality backwards compatible with existing implementations (GMail, Apple Mail, Outlook have to work or the protocol will get ignored)
• drop all useless/unpopular/insane features (can we kill UTF-7, please?)
• make de-facto standards and common extensions part of the standard (everyone uses XLIST)
• add very clear and strict implementation guidelines (IMAP is particularly bad at this and all "requirements" read like "Clients should do this, but might do something completely different")
I think the best bet is to do to "IMAP5" in the same way HTML5 has been done:
• keep basic functionality backwards compatible with existing implementations (GMail, Apple Mail, Outlook have to work or the protocol will get ignored)
• drop all useless/unpopular/insane features (can we kill UTF-7, please?)
• make de-facto standards and common extensions part of the standard (everyone uses XLIST)
• add very clear and strict implementation guidelines (IMAP is particularly bad at this and all "requirements" read like "Clients should do this, but might do something completely different")
Going RSS→Atom route is going to end like this: http://xkcd.com/927