Re:Why Turtl switched from Common Lisp to JavaScript (2019)
by gibsonf1 on Wednesday October 27, 2021 @05:37PM
(#29019454)
Woo is a superfast web server. It handles receiving 4x the number of requests that node js can. Once the server gets the request, you can control how the response works with futures etc. Our front end webapp is using Vue cli, which clearly is javascript. I assumed the discussion here was about the server, not the front end webapp on the browser.
[ Parent
| on HN ]
Re:Why Turtl switched from Common Lisp to JavaScript (2019)
by orthecreedence on Wednesday October 27, 2021 @05:50PM
(#29019555)
The discussion was about an app server written in CL (Wookie) that supports a backend app written in CL, all in async (via cl-async).
It seems to me you're using Woo as an Nginx replacement, not as a CL app server, which makes total sense to me after you described the model you're using.
Re:Why Turtl switched from Common Lisp to JavaScript (2019)
by wyager on Wednesday October 27, 2021 @06:09PM
(#29019719)
I wouldn’t describe 4x nodejs as “super fast”. Nodejs is one of the slowest popular backends, or at least it was when I did a comparison a few years ago.
Re:Why Turtl switched from Common Lisp to JavaScript (2019)
by gibsonf1 on Wednesday October 27, 2021 @06:20PM
(#29019793)
In the last benchmarks, woo beat all including the Go webserver: Scroll down just a bit to see the comparisons here: https://github.com/fukamachi/woo