I am not sure "clobbering library/framework names" is a real problem, but it does make things a bit more annoying for us mere humans. Imagine my confusion where I read a bunch of web dev types praising asdf and feeling confused only to find out asdf is now the name of some new tool. Now I have to explicitly search for "asdf lisp" to find info about the thing[0] I actually had in mind.
Well given sheer number of new css/js frameworks/libraries that are produced every week, name collisions seem like an inevitability. After all, there are only 10,830,144,982,920 strings available in
Bit off topic, but the TLS certificate seems to be wrongly issued to the wildcard *.kasserver.com, which seems to be a back-end related domain for a German hosting company with strong mid-2000 vibes named "ALL-INKL.COM" [1].
They even have a full-blown SOAP API to manage their services [2].
I used them at my parent run kita in Berlin. Very cheap! I eventually moved them to hetzner due to ssl problems but they had good support and I kept the domain with them.
It was really small and German speaking and wonderfully low tech but not anti-tech. Parent run meant we had regular meetings and had to paint, clean, organise events and vote on executive decisions like buying a dishwasher. It was really intimate and my kids learnt German really well. It was a lot of overhead but it brought us into the community well. The teachers were really dedicated they were amazing. Best start possible. Parents regularly had tensions between them but this is the nature or a random sample of population, lol.
It made me laugh imagining an "enterprise grade" commercial version of curl. What features would it have? SAML integration? Support for Kensington locks?
[0] https://asdf.common-lisp.dev/