Because Emacs is an OS the way it should be — an extensible system with a unified UI instead of a pile of separate and hardly interoperable applications.
The more time I spend with UNIX and hear the "UNIX philosophy" used in place of argument when someone doesn't like the feature set of some software, the more I realize that we need to move on from UNIX. We should take more ideas from things like Emacs and the Lisp machines when designing our software, and less from UNIX.
The modular aspects of the UNIX philosophy are pretty cool; the data interchange format (un-typed \n-delimited strings) is irrational (and
dangerous).
JSON w/ a JSONLD @context and XSD type URIs may also contain newlines (which should be escaped)
Note that, with OSX bash, tab \t must be specified as $'\t'.
And, sometimes, it's \r\n instead of just \n (which is extra-format metadata).
And then Unicode. Oh yeah, unicodë.
\r\n is Windows, not Unix.
What about Unicode? (Btw, UTF-8 was created by unixers Rob Pike and Ken Thompson https://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt )
When you're parsing a text file, or streaming lines of text delimited with /n, how do downstream programs know whether it's ASCII or unicode?
OTOH, I'll take SExps over JSON, thanks.
http://www.johndcook.com/blog/2010/06/30/where-the-unix-phil...
man page for ls and see if they built a ton onto the little program and not just write new programs.
(For some additional perspective, I don't really hate UNIX, I still recall how much of a breath of fresh air it was coming from Windows, but I think it, much like the X server, is really showing its age.)
The parent poster does have a point though, we don't have URI for emails...
My email links are formatted mu4e:msgid:<message identifier>. My git links are magit:<project path>::commit@<git SHA>. Remote files are just file:/ssh:<user>@<server>:<remote path>. You could write your own for whatever you want, gmail links say (although then you could just use a plain old HTTP link).