---

[1] https://assets.mozilla.net/annualreport/2022/mozilla-fdn-202...

Now, your process might depend on other system resources like input and output; as this event is also a process, it also has a file descriptor, which will be attached to your process in the file descriptor table.

What event? Are input and output an event? Why is this event its own process? Input and output are not a process are they?

Also, does a process have its own file descriptor table? That was never mentioned before and this reads like it is already known.

This sort of stuff goes on in my head throughout the entire article...

It's also still unclear to me what happens if multiple processes try to access the same file. Do file descriptors help to lock files during writing?

It might come off as a cost saving short term, but I doubt in the end the catalogues did not bring in enough money anymore.

I use Windows + WSL even though I practically never do anything Windows related.

I haven't done a manual deployment since. I hope it got significantly better and I may be an idiot but the reputation isn't fully undeserved.

The problem back then was also that this was usually the first thing you had to do to try it out. Doing a complicated deployment without knowing much about it doesn't make it any easier.

- Unless the function is extremely clear like max() or min(), you will have to read the function and jump around the code. I feel people underestimate the cognitive overhead required for this. This gets worse the more arguments are required to pass around. Linear code is much easier to read.

- More lines of code, a comment adds 1 line while a function or method adds at least 4. Also, code that has to be separated over multiple functions is practically always longer than linear code. Doing this to the extreme can have quite an effect.

- Naming issues, it can be hard to think of a good name for a function and it almost never describes it perfectly. Misnaming things leads to bad assumptions and leaky abstractions. Comments have the luxury of potentially conveying more information and are also less important to get right.

If you use a lot of vertical scrollbars then by all means go ahead and abstract it, but I'd generally pick the comment.

  services:
    foo:
      image: foo/bar:6.9
      user: ${UID:-1000}:${UID:-1000}

ZSH or other shells don't necessarily set $UID, so if you're running Linux, not id 1000 and not running Bash you might need a little .env file with `UID=1001` in it to make it work. And then the user is still nameless in the container. This is kind of rare and I only use it for dev containers where most relevant files (and permissions) are bind-mounted from the host, so it hasn't really been a problem in practice.

Remaps would be cleaner but I find it too much work to explain for normal developers just wanting to use a dev container.