I've thought about this also. The "batteries included" philosophy (Python a good example of this or CL's "alexandria" library), would help welcome new users getting started quickly, which seems more of a bigger factor for language adoption these days, and reduce duplication of effort. In addition, I think this would be more effective with PicoLisp since there is a BDFL, unlike CL which makes it difficult to come to a consensus.
Not to derail the OP, but in the same vein of thought, another critical element is a "quicklisp" library, which would be a tremendous boon to the ecosystem. However, all of this becomes more of a factor as the community grows. This would be a good topic for the upcoming meeting :) On Thu, Jun 18, 2020 at 11:57 AM <andr...@itship.ch> wrote: > Hi aw > > Awesome, many thanks. > > I will definitely build upon this. > Good if we can re-use and establish some standard picolisp libraries > (beside/in addition to the ones in the distro). > NIH syndrome etc. > > Cheers, > beneroth > > On 18.06.20 12:27, Alexander Williams wrote: > > Hi all, > > > > It's been a busy week, this time i'm announcing another open source > > release: > > > > picolisp-supervisor: https://github.com/aw/picolisp-supervisor/ > > > > It's a program I created almost 4 years ago to copy Unicorn[1], but > > which was not suitable for public release. I've tweaked it, wrote some > > documentation (and comments), and decided to share the code with > > others who may be interested. > > > > The source code is published under the MIT license. > > > > PS: Also check out my other project released earlier this week[2] ;) > > > > Cheer, > > > > > > AW > > > > - [1] https://yhbt.net/unicorn/ > > - [2] https://github.com/aw/picolisp-kv > > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
