News for hackers. Stuff that matters.
Re:This Old Lisp by blue1 on Friday October 19, 2018 @11:29AM (#18257378)
I know it is easy. In this particular example, it is also trivial to write it from scratch.

But, if UIOP:STRCAT is such a "standardized" solution as you claim, then I believe it should become part of a (hypothetical updated) Standard, not a second-class citizen behind a member of the ancient aristocracy like Lord CONCATENATE.

What I mean is that I think there should be some kind of mechanism so that standardized solutions emerge (from widely used libraries for example) and become part of the Standard. Like it happily happens in many other domains.

Re:This Old Lisp by junke on Friday October 19, 2018 @12:08PM (#18257705)
In Go, in Javascript, in Python, in C++, you have the luxury of having thousands of people who just implement things for you while you sleep. See the list of "gold members" for the Standard C++ Foundation: https://isocpp.org/about. See the list for Python: https://www.python.org/psf/sponsorship/sponsors/

There are people whose jobs is to work on that.

When you write "it should become part of a standard", you use the passive voice: who is going to do it?

In CL, the effort is focused on things that matter to each individual, or each company that uses it, and sometimes a (de-facto) standard library comes to life.

Re:This Old Lisp by phoe-krk on Friday October 19, 2018 @11:50AM (#18257576)
I never said that the updated standard should not happen - quite the contrary. I'm saying only that a string contatenation function is already available on every modern Lisp image that has ASDF loaded, and is therefore usable from user code.