>, keep email for communication? Again, stop breaking it.
It's a matter of a different perspective and "breaking it" is in the eye of the beholder.
For many end users of email (and Google Inc's point-of-view apparently), it's the other users sending me emails that's "breaking it" beyond SMTP's original design intentions.
>Use CalDAV for tasks sync,
E.g. it's the other users who send "tasks" and "appointments" inside a freeform email instead of strictly using CalDAV. Their abuses of email has broken the SMTP system. If overloaded email usage by other humans who don't categorize what they send into strict protocols such as CalDAV is a fact of life, the Google response is to add some complexity to the UX/UI to let users conveniently copy paste it into the sidebars for Tasks and Calendar. Google may be wrong (as the blog post argues) but I think it's worth entertaining the idea that the multipurpose usage of email has already "broken email".
For many people, your suggestion of putting 17k of emails into a single namespace alongside other important emails is not acceptable. They want a UX/UI to make a first crude pass at filtering it into a hierarchy. This does have a negative side effect if "hiding" it from some users who don't notice it's there.
It's a matter of a different perspective and "breaking it" is in the eye of the beholder.
For many end users of email (and Google Inc's point-of-view apparently), it's the other users sending me emails that's "breaking it" beyond SMTP's original design intentions.
>Use CalDAV for tasks sync,
E.g. it's the other users who send "tasks" and "appointments" inside a freeform email instead of strictly using CalDAV. Their abuses of email has broken the SMTP system. If overloaded email usage by other humans who don't categorize what they send into strict protocols such as CalDAV is a fact of life, the Google response is to add some complexity to the UX/UI to let users conveniently copy paste it into the sidebars for Tasks and Calendar. Google may be wrong (as the blog post argues) but I think it's worth entertaining the idea that the multipurpose usage of email has already "broken email".
For many people, your suggestion of putting 17k of emails into a single namespace alongside other important emails is not acceptable. They want a UX/UI to make a first crude pass at filtering it into a hierarchy. This does have a negative side effect if "hiding" it from some users who don't notice it's there.