6 ms·
Reminds me of Greenspun's tenth rule of programming (also counts for Java, but this most probably predates it): Any sufficiently complicated C or Fortran progr
by hondadriver 2y ago
Reminds me of Greenspun's tenth rule of programming (also counts for Java, but this most probably predates it):
Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule
- wavemode 2y ago> Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp. ...including Common Lisp.
- mjburgess 2y agoRitchie's Revenge: And this half is still faster than Common Lisp.
- pjmlp 2y agoOnly when adding UB exploits done by optimizing compiler backends. I am old enough to remeber the days any junior Assembly programmer could easily outperform any machine code generated by the C compilers of the day.
- masijo 2y agoSBCL (the most popular Common Lisp implementation) is pretty darn fast, being comparable to Java, Go or OCaml. https://benchmarksgame-team.pages.debian.net/benchmarksgame/ https://benchmarksgame-team.pages.debian.net/benchmarksgame/
- mjburgess 2y agoBut still slow compared to a non-GC'd language. Walking over all the references of your program while its stopped is slow.