>>221
Btw the easiest way to do this is centering around
pre-existing package ecosystem like Chicken Eggs.
1.Add Stalin Scheme optimizations to Chicken Scheme(effectively steal everything possible and make it Chicken Eggs compatible),
or fork Chicken Scheme to promote a new project which will reuse the Chicken Eggs ecosystem.
2.Adopt srfi-110 aggressively and promote it in programmers forums:
don't mention any parens based code(just imagine parens soup as toxic garbage programmers feel disgust at).
3.Promote your fork or Chicken Scheme itself aggressively as new
language superior to lisp(mention the easy Python syntax, Fast executables and Lots of Libraries)
4.Write heavily requested libraries yourself.
Determine what the popular libraries are and fork them into Chicken Egg packages.
5.Write some tutorials with Python-like syntax.
Tutorials, examples, manuals create a huge interest from new programmers - old programmers are settled in their prefferred ecosystems/libraries and switching to X has a high psychological cost. The target is new programmers without much dependence on their software ecosystem: think people who wrote a few scripts here and there, but didn't yet develop strong preference for some paradigm.
6.You have now resurrected LISP from AI winter.