[ksaj]

Judging by the name, the exciting part is the framework it was written on. As a habit, I do not use software that relies on code association in the name as a selling point. A lot of new coders use this naming convention, as they've become excited cheerleaders for their platform of choice (especially if it is a recent language or framework). But how much do actual users care about the underlying technicals? Why make the software sound like it is part of the language or framework when it isn't?

Imagine if there was an InlineAsmGrub to compete against that other GRUB. It's just that silly a practice.

[arvyy]

I see where you're coming from, and the naming was quite unimaginative, indeed. I saw that "truffle ruby" called itself that and copied it.

However, the fact it's based on truffle is the selling point -- truffle enables interop between languages on the framework. So, for example, you can take truffle JS implementation, import express library or whatever, and then as part of the implementation do

````

let fn = Polyglot.eval('islisp', '(lambda (x) (+ x 1))');

fn(1);

````

(toy example. But this interop can happen in all directions, it's not limited to js but can be used from truffle python, ruby, java, etc; and it also isn't limited to just primitive values, you can pass around functions as well).

If you aren't looking for a specifically a truffle lisp, it would make more sense to use one of the established common lisp implementations.

[medo-bear]

I think the name is good. It took me a whole second to figure out its selling point, especially since there is a new "lisp" being made every day. Fancy names are exciting for like a millisecond. Good luck with the project! Im a Common Lisp user but this seems like a plausible alternative to Clojure and even ABCL

[nirvdrum]

When building an alternative implementation of a language you're a bit hamstrung by the name. You could come up with something completely novel, but no one is ever going to discover or use your software. So, it's quite common to integrate the language name into your software name somewhere. The next question then is how to differentiate. Oftentimes the underlying framework is really the selling point. JRuby is Ruby on Java. TruffleRuby is Ruby on Truffle+Graal. It's easy for people to quickly identify and understand the difference. Instead of calling it TruffleRuby, I suppose we could call it PartialEvaluationRuby or SuperFastRuby, but those naming conventions have their own flaws.

Do you have a suggested naming convention to follow? There's a rich history of alternative language implementations following the convention you dislike, but I think those involved would be open to an alternative.