Tangential: if we're talking Lisp and native code speed, Steel Bank Common Lisp (by default) compiles everything to machine code. [0] https://sbcl.org. - Source: Hacker News / 9 months ago

Q5: Get http://sbcl.org/. Install https://quicklisp.org/. SBCL is the implementation that's the lowest friction, and Quicklisp is a package manager that's almost* painless. Source: about 1 year ago

That is what we do in Lisp. Try sbcl if you haven't tried it yet. Source: about 1 year ago

I want to add the sbcl-doc subpackage (the manual for SBCL in GNU Info format), but first I need to understand how to write package definitions. As far as I understand there are the "templates" which are shell scripts that describe how a package is to be built and installed, and xbps-src is a shell script which can process these templates to actually carry out the work. Source: over 2 years ago

> Lisp looks like Python, that's far from C, and usually it's a "interpreted" language, far from machine the currently most popular Common Lisp implementation is based around an optimizing native code compiler. That compiler has its roots in the early 80s. See https://sbcl.org . It's far away from being 'interpreted'. - Source: Hacker News / almost 3 years ago

It would be awesome to develop something abstract and useful for usage as common PL (besides just solving specific problem), but it's really hard to develop a general purpose language (with memory management, mutations, etc.). For example, at my work I built reactive library mostly similar to Rx.js or Bacon.js, but with additional ability to compose different reactive systems on top of each other, so that... Source: over 2 years ago