(2014)
SBCL: The Assembly Code Breadboard
21–23 of 23 posts
Re: SBCL: The Assembly Code Breadboard
#22I used SBCL for an algorithmic trading framework for EXACTLY this reason. More precisely, this was SBCL/ANSI C application where most of the application was implemented in Common Lisp, some OS / low level stuff was written in ANSI C and same things were written in Lisp to compile to machine code and inserted into "C world". There would be no Common Lisp virtual machine on the critical, low latency path. Instead, the…
Very cool story; thanks for sharing! I think a major fault in the industry is "find somebody who's good at X". It's not a necessary or even optimal requirement. Common Lisp doesn't have too many particularly odd language features; I'd say learning the Rust borrow checker or Scheme's call/cc is more difficult than anything Lisp has to offer. What organizations need to do is prepare to let smart engineers self-train on…
"Anyone could learn Lisp in one day, except that if they already knew Fortran, it would take three days." — Marvin Minsky
Re: SBCL: The Assembly Code Breadboard
#23Earlier quoted context omitted.
Very cool story; thanks for sharing! I think a major fault in the industry is "find somebody who's good at X". It's not a necessary or even optimal requirement. Common Lisp doesn't have too many particularly odd language features; I'd say learning the Rust borrow checker or Scheme's call/cc is more difficult than anything Lisp has to offer. What organizations need to do is prepare to let smart engineers self-train on…
"Anyone could learn Lisp in one day, except that if they already knew Fortran, it would take three days." — Marvin Minsky
The irony there is that someone first had to learn enough Fortran to invent the FLPL (Fortran List Processing Language) system that went on to inspire the impelmentation techniques and terminology of Lisp.