4 ms·
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
by noobermin 4y ago
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.
[0] https://asdf.common-lisp.dev/ https://asdf.common-lisp.dev/
- Dylan16807 4y agoOn the other hand I'd say that no tools should be named asdf or other keysmash, except for ZXCVBN.
- sshine 4y ago> except for ZXCVBN You mean the Low-Budget Password Strength Estimator? https://github.com/dropbox/zxcvbn https://github.com/dropbox/zxcvbn Yeah, that name is totally legit.
- marginalia_nu 4y agoWell 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 [a-z0-9]{1,8}(\.js|\.css)? It's basically IPv4 without ICANN.