[noobermin]

Wait, not only is it called asdf leading to confusion, it literally is also a package manager of sorts just like the original asdf???

I just tried googling it having not really used CL in a while, and apparently it was seo'd to the top of google results too?

[000ooo000]

One of my pet peeves with tooling these days is the completely random naming. Literally no effort made, whatsoever, to come up with something vaguely descriptive. Neovim plugins are the worst for this. They're comically badly named.

[out-of-ideas]

agreed, but i know firsthand words are hard, and names are more specific words and can be very hard (especially for developers) - esp with shorter names ,and will have a higher chance of a name collision

[brabel]

I raised this complaint before and learned that most people using the "new" one have never even heard of Common Lisp, and certainly not of its own "asdf" system.

[lispm]

And the possibility of using "Google" to check for name collisions seems not to be known...

[juunpp]

The possibility of existence of a "programmer" that is completely oblivious to Common Lisp is the really interesting phenomenon to ponder here. But hey, at least the article links back to Hacker News, Mastodon and Reddit so that we can all revel in ignorance. Surprised there is no Discord.

[bandrami]

Came here to ask that. I've used the CL ASDF for decades now and have been confused more than once to run across docs for this one instead.

[phinnaeus]

What's the "original asdf?"

[ReleaseCandidat]

https://asdf.common-lisp.dev/

[guenthert]

https://en.wikipedia.org/wiki/Another_System_Definition_Faci...

(it's bit like Python stealing the name of a CL compiler ...)

[bmitc]

asdf is not Python specific.

[Y_Y]

Correct, asdf will work with other Common Lisp compilers.

[bmitc]

:|