13 comments

[ 58.4 ms ] story [ 781 ms ] thread
I'm no expert, but could it be that one contributing factor to the speed is that neovim stores the files in ram while Nginx has to go to disk for every request?
I like that the author put it on a subdomain, probably a smarter move. I have an old laptop I keep installing Linux on and not deciding what I want to do with it. Maybe I should build quirky web servers on it..
I recently had a lot of fun while playing with nixos using claude code.
For me it resolves to 198.74.55.216 which is a Linode USA IP. No IPv6.

No mention of why it needs to go through a Linode server.

Also if for some reason you get DDoSed you can probably switch that VPS a lot quicker than getting a new static IP at home, if at all.
This is what I love HN for. "Your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should".

This awakens things I've been thinking about Neovim for a while now: now that libuv is embedded, there's really no reason not to use it as a cross-platform application runtime (except for the fact that that's horrific).

(comment deleted)
This has to be one of my favorite hacking articles I’ve read on HN. The analysis, concept, and execution :chefskiss:
That's a fun article. As for the 'is this even safe' angle: this article should be the go-to example for anybody that thinks that their code will never be run in the context of unchecked requests coming in over the network because that would make no sense at all.
This is the kind of stuff that made me like HN initially. Great job