#lisp #lispyGopherClimate we are going to be joined by (MIT AI lab, Harlequin, ANSI CL) @kentpitman on the live show in two and a half hours.
Are there any particular requests or thoughts for topics.
Post
#lisp #lispyGopherClimate we are going to be joined by (MIT AI lab, Harlequin, ANSI CL) @kentpitman on the live show in two and a half hours.
Are there any particular requests or thoughts for topics.
@kentpitman someone ~asked for general thoughts on usability design to me in a DM.
another thought I am interested in @kentpitman 's opinion about might be (re)invigorating, for example, #lispGameJam or #lispGames otherwise. This autumn there were only 20-odd one-week-game-jam submissions and only one in ANSI #commonLisp. Looking at the Tiobe index, lisp as such slid from #2 ("most popular")) in 1985 to #24 "more popular than COBOL" in 2025 https://www.tiobe.com/tiobe-index/ .
@screwlisp My impression is ANSI Common Lisp is still stuck in the perception of bloat, lack of purity, design by committee, and preconceptions over CLOS and/or OOP. Which is ironical given the sizes of modern batteries included languages.
To overcome these perceived issues people constantly seek new dialects or languages, and may end up reinventing a lot of Common Lisp wheels.
@screwlisp have you considered the possibility that common lisp is poorly designed? r?rs too.
picolisp is simple (maybe too simple). janet is pragmatic and easy to embed. You can tell those communities to join.
A space for Bonfire maintainers and contributors to communicate