These wounds appear to be self-inflicted.

i thought it was neat how php lets you write your website's logic with the same directory tree pattern that clients consume it from, but i didn't want to learn php so i made my own, worse version

You live like this?

I've taken some precautions, it's running in a container as an unprivileged user and the only writable mount is the directory where make writes rendered pages, but i probably should move it into a vm if i want to be completely safe lol

Seek help.

yeah, templates can be parsed at compile time but these frameworks are not embeeding whole fucking prerendered static pages/assets

Blog content was stored in memory and it was served with zero-copy to the socket, so yea, it's way faster. It was before times of php-fpm and opcache that we're using now. Back then things were deployed and communicated using tcp sockets (tcp to rails, django or php) or reading from a disk, when the best HDDs were 5600rpm, but rare to find on shared hosting.

The answer is no. The more file is used the longer it sits in kernel filesystem cache. Getting file from cache versus having it in process memory is few function calls away all of which takes few microseconds. Which is negligible in comparison to network latency and other small issues that might be present in the code.

On few of our services we decided to store client configuration in JSON files on purpose instead of running with some sort of database storage. Accessing config is insanely fast and kernel makes sure that file is cached so when reading the file you always get fast and latest version. That service is currently handling around 100k requests a day, but we've had peaks in past that went up to almost a million requests a day.

Besides when it comes to human interaction and web sites you only need to get first contentful paint within one second. Anything above 1.5s will feel sluggish, but below 1s, it feels instant. That gives you on average around 800ms to send data back. Plenty of time unless you have a dependency nightmare and parse everything all the time.

Very, very bad Ansible.

I wrote my webserver in pure bash.

bash -c "python -m http.server 8080"

Let's just get this out of the way

no, you'll also have to learns each libraries special quirks on your OS

Still don't do this. If you use bash specific syntax with this head, that's a bashism and causes issues with people using zsh for example. Or with Debian/*buntu, who use dash as init shell.

Just use #!/bin/bash or #!/usr/bin/env bash if you're funny.

No no no no no, do not believe this you will shoot yourself in the foot.

https://wiki.debian.org/Shell

Beginning with DebianSqueeze, Debian uses Dash as the target of the /bin/sh symlink. Dash lacks many of the features one would expect in an interactive shell, making it faster and more memory efficient than Bash.

From DebianSqueeze to DebianBullseye, it was possible to select bash as the target of the /bin/sh symlink (by running dpkg-reconfigure dash). As of DebianBookworm, this is no longer supported.

It is a symlink, but bash will automatically enable posix compliance mode if you use it. So any bash specific features will bomb out unless you explicitly reset it in the script.