Earlier quoted context omitted.
Hello! I'm one of the Urbit devs. 1. Has this ever actually happened? I'd be quite disturbed by that. We're more than happy to have people learning about Urbit, although we're not particularly active on social media. 2. Curtis is certainly controversial. None of us share his views, but we do enjoy working together. I'd like to think we live in a world where people who don't agree can still collaborate professionally.…
> Hello! I'm one of the Urbit devs. Can you please explain to me what a "non-lambda interpreter" is and why it matters?
It matters because gensyms suck. More generally, if you are building a two-layered system in which a compiler targets the interpreter, symbols, functions, and scopes are concepts that belong in the high-level language, not the low-level interpreter. (I think Shen is one example of a typed Lisp that targets an untyped Lisp, but obviously I know nothing about Lisp.)
So the lambda calculus is a classic layer violation.
Where I went to school in operating systems, which was Brown and Berkeley, we were taught to avoid layer violations and always separate mechanism from policy. Not sure what Lisp people are or were taught -- honestly, there were not a lot of them left, even in the '90s -- but it never seemed to include this.
I always look at a stateful Lisp machine, or Emacs, or whatever, and see a giant structureless blob of symbols. That said, this is probably a totally unjustified prejudice on my part, and at this point I really have no excuse except lack of time for refusing to learn more.