It was pretty obvious what was happening; naming your fictional debate partner after the most famous pseudonym of all time is as transparent as you can get. There's a long history of people doing exactly this in a variety of fields; it's not deception.
The name was "Nickieben Bourbaki", a reference to the collective pseudonym "Nicholas Borbaki" of the French mathematician collective. RPG had the idea that other people at Lucid would be interested in participating under this collective name, but that didn't happen.
>I don't think so, we now call that kind of behaviour a sock puppet account. Why the deception?
When did "looking at both sides of an argument" fall out of favor? It's a practice advised by science, philosophy, politics, all the way back to Plato's dialogues and earlier (which also used different names to present the views) all the way to "Godel, Escher, Bach".
>a sock puppet account
Sock puppet accounts are fake accounts made to seem as many people are in favor of a specific point X. They're meant to amplify X's perceived adoption.
It's not about a single person debating both sides of an argument (X and -X).
In fact, debating also for the opposite of your point, would be close to an opposite of a sock puppet account.
So is Lisp in good shape today? See some cool releases of this year: https://www.reddit.com/r/Common_Lisp/comments/rp5lik/what_wa... CLOG (GUI in browser), M1 support for SBCL, LispWorks 8, VSCode plugin, Coalton (ML on top of CL), SB-SIMD and many new improvements to SBCL, new Clozure version, we know of more companies using CL...
I don't think so. Where are the "stupid and wrong by default" examples in Python that are fixed with heroic effort in Julia? Julia has a lot of features that make it attractive, but Python of course does as well. The one big example I can think of that Python has suffered from over the years is the GIL.
The big one is package management. Julia's package manager is one of the best in the world (along with Rust). Python has about 20, and they all kind of suck.
Threading is another.
There's also a bunch of smaller things (e.g. no local eval) that are more tradeoffs for performance than straight up wins.
I read something here about lisp, that it was too good at letting you make whatever you wanted that libraries that 'carry' other programming languages didn't pop up and that had adverse affects on popularity, etc. If someone remembers this and has the link that would be great.
https://cs.stanford.edu/people/eroberts/courses/cs181/projec...
Summarized as:
"When tradeoffs are required in a software system, priority should go to implementation simplicity at the expense of completeness or correctness."
See also the wikipedia article:
https://en.wikipedia.org/wiki/Worse_is_better
An interesting aspect of all this is that Gabriel argues with himself in a series of papers under a false name:
https://dreamsongs.com/Files/worse-is-worse.pdf
A great example of someone looking at both sides of an argument.