I haven't been following this so closely, but the articles I have read seem to position these proposals as changes to e-mail as a system, if not as a protocol. I leave thinking the authors want to do something radical, to alter something longstanding, to go up against giant, ingrained players and conventions.
I don't think this post would have happened if we were instead hearing more about "new ways to use e-mail," or "adding functionality to an email client." I think the narrative is more like, as others in the thread have referenced, PG's frighteningly ambitious ideas, more like visionaries who are daring to challenge something so established.
Making a new email client that has some extra features is one thing. Changing email forever is another. I think that's what the post is reacting to.
Edit: and, anyway, I think sharpening the discussion by invoking the difference between the client and the protocol is useful, and hopefully will make future conversations about this more clear.
I think PG is in the minority when he considers a conversation over email a "degenerate case" of a TODO list item. A public-writeable personal todo list application is separate from my email client, whether it uses the email protocol to send todo items, or a new protocol to send todo items, or http to put todo items on a centralized database, etc.
Can anyone offer some links to recent/current projects that want to "fix" email by changing the protocol?