Re:Why Turtl switched from Common Lisp to JavaScript (2019)
by orthecreedence on Wednesday October 27, 2021 @05:25PM
(#29019332)
Yeah, admittedly I could have gone with threading/hunchentoot and been much better off. It was probably stupid to forge the entire async path the way I did.
To be fair, Turtl these days gets enough traffic where async does probably make sense for us, and nodejs is serving us well.
To be fair, Turtl these days gets enough traffic where async does probably make sense for us, and nodejs is serving us well.