Why Not: From Common Lisp to Julia

CommunityNews · 9 September 2022 13:48

not-common-lisp-to-julia.org.
GitHub Gist: instantly share code, notes, and snippets.

Read in full here:

gist.github.com

https://gist.github.com/digikar99/24decb414ddfa15a220b27f6748165d7

not-common-lisp-to-julia.org

#+title: Why not: from Common Lisp to Julia

/This article is a response to mfiano's [[https://mfiano.net/posts/2022-09-04-from-common-lisp-to-julia/][From Common Lisp to Julia]] which might also convey some developments happening in Common Lisp. I do not intend to suggest that someone coming from a Matlab, R, or Python background should pickup Common Lisp. Julia is a reasonably good language when compared to what it intends to replace. You should pickup Common Lisp only if you are interested in programming in general, not limited to scientific computing, and envision yourself writing code for the rest of your life. It will expand your mind to what is possible, and that goes beyond the macro system. Along the same lines though, you should also pickup C, Haskell, Forth, and perhaps a few other languages that have some noteworthy things to teach, and that I too have been to lazy to learn./

/I also do not intend to offend anyone. I'm okay with criticizing Common Lisp (I myself have done it below!), but I want the criticism to be done correctly. If I had to wish something from Julia, it would be to provide a way to turn off runtime optimization to (radically) speed up compile times for purposes of debugging./ 

* Table of Contents
:PROPERTIES:
:TOC:      :include all
:END:

This file has been truncated. show original

This thread was posted by one of our members via one of our news source trackers.

bot · 9 September 2022 13:48

Corresponding tweet for this thread:

Share link for this tweet.