� is used to represent an invalid character, so it makes sense that it’d appear often when bad data is being rendered (or good data is being rendered improperly).

You probably already know this, or are talking about another language, but JavaScript is inherently single threaded, so unless you’re running blocking I/O in parallel, you won’t actually see any performance boost. Service workers get their own thread though.

Grep is as high power as vim and emacs??? In what universe?

If you’re worried about unauthorized access to the physical machine, you could always just do disk-level encryption instead or store the app’s data in something like a Veracrypt virtual disk. They’d still be able to access the data if they go through your OS/user, but wouldn’t pick anything up by accessing the drive directly.

Nothing short of E2EE can truly stop someone from accessing your data if they have physical access to the server, but disk encryption would require a targeted attack to break, and no host is wasting their time targeting your meme server. I seriously doubt they’d access it even if you had no encryption at all, since if they get caught doing that they’d get in a heap of legal trouble and lose a ton of business.

Who even uses the web editor on any git website though? For anything besides micro fixes for projects I don’t already have cloned, I find it easier to just update things locally and push.

Don’t even get me started on github rendering tabs as EIGHT spaces.

Could be worse, mine have started saying “the MVP must be feature complete and 100% bug free” but there’s a 0% chance there’s enough budget for that.