Making email more modern with JMAP
So, how long until everything is JSON-shit over port 80 and how long until port 80 is old news and only port 443 is used for anything and everything?  I can&#x27;t claim to be familiar with IMAP, but it can&#x27;t be worse than this garbage that requires an HTTP client and a JSON parser.<p>To process JSON, you must inspect every character, which is reason enough it&#x27;s an awful &#x27;&#x27;format&#x27;&#x27; that only an ignorant could hold dear.  Douglas Crockford brags about how smart he is for disallowing comments, but there&#x27;s whitespace allowed everywhere.  Let&#x27;s not forget this asinine integer nonsense, because JavaScript lacks real integers.<p>I&#x27;m sure most people think HTTP clients and JSON parsers are standard-library affairs, nowadays, though; let&#x27;s just entirely ignore matters of licensing and whatnot.<p>It&#x27;s disgusting to see this as an IETF standard, but people have been complaining about how that moves along for decades; take a look at Google&#x27;s robots.txt &#x27;&#x27;standard&#x27;&#x27; that doesn&#x27;t do anything useful and effectively makes every existing file standard, rather than do much of anything worthwhile.  The WWW and JavaScript are nothing more than a continuation of this worse-is-better filth that UNIX and C previously championed; decades ago, the IETF revised the RFC for the Finger protocol and warned about security, solely because some idiot wrote a shitty Finger server in C; now, we have useless and unnecessary standards such as this that only serve to further this next generation of idiocy.<p>I wonder when all of this will finally collapse under its own weight.