Contains an answer to this question:

Neil, you've written a trans woman character in Sandman but the way the story develops makes it seem like you think trans women arent actual women. And well, considering what you said about your friend, im sure thats not the case. So... could you clarify things? (i hope this doesnt sound accusatory, thats not how i mean it)

So many of the comments in this thread really hit home, and put into words my experiences, in ways I'd never be able to. I really wish I had the ability to explain like this.

What's really helpful here is it's healing to see people talk about exactly the things I went through. It's sort of reassuring to know you're not alone, you didn't imagine it, that it really did happen.

A favourite episode of QED from my teens, where a RAF Hawk flew round the coast of mainland Britain. The show itself is about 1/2 hour long, and concentrates very much on the changing geology. The flight itself is sped up about 10x, making it a mach 10 flight, give or take.

Very BBC. Very 80s. Very cool for the time.

If you found a leak of data from the NHS and let them know, you'd think they'd be properly happy about being told, right?

About that...

While Emacs proponents largely agree that it is the world’s greatest text editor, it is almost as much a Lisp machine disguised as an editor. Indeed, one of its chief appeals is that it is programmable via its own programming language. Emacs Lisp is a Lisp in the classic tradition. In this article, we present the history of this language over its more than 30 years of evolution. Its core has remained remarkably stable since its inception in 1985, in large part to preserve compatibility with the many third-party packages providing a multitude of extensions. Still, Emacs Lisp has evolved and continues to do so.

Important aspects of Emacs Lisp have been shaped by concrete requirements of the editor it supports as well as implementation constraints. These requirements led to the choice of a Lisp dialect as Emacs’s language in the first place, specifically its simplicity and dynamic nature: Loading additional Emacs packages or changing the ones in place occurs frequently, and having to restart the editor in order to re-compile or re-link the code would be unacceptable. Fulfilling this requirement in a more static language would have been difficult at best.

One of Lisp’s chief characteristics is its malleability through its uniform syntax and the use of macros. This has allowed the language to evolve much more rapidly and substantively than the evolution of its core would suggest, by letting Emacs packages provide new surface syntax alongside new functions. In particular, Emacs Lisp can be customized to look much like Common Lisp, and additional packages provide multiple-dispatch object systems, legible regular expressions, programmable pattern-matching constructs, generalized variables, and more. Still, the core has also evolved, albeit slowly. Most notably, it acquired support for lexical scoping.

The timeline of Emacs Lisp development is closely tied to the projects and people who have shaped it over the years: We document Emacs Lisp history through its predecessors, Mocklisp and MacLisp, its early development up to the “Emacs schism” and the fork of Lucid Emacs, the development of XEmacs, and the subsequent rennaissance of Emacs development.