Re: Future of PicoLisp?

2017-02-23 Thread Alexander Burger
Hi Erik, thanks for the long post! Just in short: > 'Learn PicoLisp the Hard Way' I totally agree. This would be a great project, I'm ready to join. Same for Stack Overflow support. > And let's make sure said landing page is served over HTTPS. It's 2017. Yes, yes, I know ;) In fact, it is

Re: Future of PicoLisp?

2017-02-23 Thread pd
On Fri, Feb 24, 2017 at 1:14 AM, Erik Gustafson wrote: > > > 'Learn PicoLisp the Hard Way' > > What do you think? > I think it's a terrific idea and I'm volunteer to work on it > > > Let's build picolisp.com from scratch. Still in written in PicoLisp, duh! > Make

Re: Subscribe

2017-02-23 Thread Erik Gustafson
Hi Chuck, Welcome to the community :) Just curious, what led you to PicoLisp? Best, Erik On Feb 23, 2017 8:16 PM, "Chuck Jackson" wrote: > I've spent several days looking into PicoLisp. It looks very good. > Thanks > Chuck Jackson >

Subscribe

2017-02-23 Thread Chuck Jackson
I've spent several days looking into PicoLisp. It looks very good. Thanks Chuck Jackson

Re: Future of PicoLisp?

2017-02-23 Thread Erik Gustafson
Hey all, Another long post. TLDR: leave the core language development strategy untouched, re-redo the website, and migrate documentation to GitHub/Stack Overflow. Re: Git(Hub) for the core language... I'm also on Alex's side here. His time for core development is invaluable. We would be wise

Re: Future of PicoLisp?

2017-02-23 Thread Joh-Tob Schäg
T Am 23.02.2017 22:52 schrieb "Lindsay John Lawrence" < lawrence.lindsayj...@gmail.com>: > I am relatively new to picolisp, with limited knowledge of its development > history... but I'll politely disagree with some suggestions here regarding > making the core more 'popular' and open to

Re: Future of PicoLisp?

2017-02-23 Thread Alexander Burger
Hi Jakob, Rowan, thanks for the good hints! > "alea iacta est". However - just in case you are not already aware - > since version 2.2.2 git now only updates modification times on > *changed* files during checkout (see >