News for hackers. Stuff that matters.

A comment on Websocketd. Parent comment

Re:Websocketd by TickleSteve on Saturday January 26, 2019 @08:24AM (#19006172)
I find it ironic that people will complain about milliseconds for a fork and talk about the time for context switches... and then serve their pages using an interpreted language that is an order of magnitude slower than it could be in a compiled language...
[ Parent | on HN ]
Re:Websocketd by rowanG077 on Saturday January 26, 2019 @01:53PM (#19007738)
Who did that? I saw no one talking about interpreted languages here.
[ Parent | on HN ]
Re:Websocketd by marcosdumay on Sunday January 27, 2019 @10:40AM (#19012047)
The comment immediately below the GP that claims that performance is relative literally says that you don't have to care about forking in Node.js.
[ Parent | on HN ]
Re:Websocketd by ibotty on Friday February 01, 2019 @03:47AM (#19052632)
Not defending node.js, but it is not interpreted but run with jit compilation.
[ Parent | on HN ]