Yup! The kernel will pull the page from disk and keep it in its disk cache in RAM. Since the kernel is solely in control of what gets written to disk it can be sure it doesn’t become stale, just “dirty” when it gets updated. It will then flush it to disk, but still keep active, hot pages in memory.
Yes, neither Nginx nor Neovim should be hitting the disk when serving the requests.
One difference I can imagine is context switching due to system calls. If Nginx incurs a context switch when it calls into the kernel for the disk cache, then it suffers a performance penalty. Neovim avoids this because the file contents are loaded into a table. When requests are served, getting the content is done fully in userspace.
I have no idea if this actually accounts for the performance difference though.
I'm wondering if the usage of an em-dash in the article (somewhere towards the middle) is self-aware trolling, or just the result of excessive ai use...
> includes both a human and a computer—and “surprisingly,
Maybe I'm not adventurous enough, but I would never open an Apple product without a teardown video/instructions at hand. iFixit is a fantastic resource if they have covered your device previously.
I didn't know that about Maps and Chrome. I did know Android was an acquisition, and that YouTube was, but in both cases I think Google's put in enough work not to dismiss them as Google projects.
