It's 2023, so of course I'm learning Common Lisp

Re:It's 2023, so of course I'm learning Common Lisp by dleslie on Thursday July 27, 2023 @02:33AM (#36889746)

The classic lisp way is to build a runtime image by editing the image while running it, then dumping a binary. You never specifically need to load a source file.

But you can't easily collaborate with that style of development.

[ Parent | on HN ]

Re:It's 2023, so of course I'm learning Common Lisp by foobarbaz33 on Thursday July 27, 2023 @09:00AM (#36892763)

With lisp you typically develop in source files, versioned with Git. The same as any other language. Source files and live development are not mutually exclusive. SLIME can send code snippets from your file over to the REPL for live development. You have your cake and eat it too.

The REPL (or scratch buffer) is typically used for testing/observing. Not the actual source code development. Although it is possible to never write your source code to a file if you're just playing around with a toy experiment.

[ Parent | on HN ]

Re:It's 2023, so of course I'm learning Common Lisp by kgwgk on Thursday July 27, 2023 @09:26AM (#36893127)

> The classic lisp way is to build a runtime image by editing the image while running it, then dumping a binary. You never specifically need to load a source file.

Says who?

[ Parent | on HN ]