Ngl this looks like astroturfing to me too

There's a lot more to an application than its configuration. It may require certain specific system libraries, need a certain way of starting up, or a whole host of other special things. With a container, the app dev can precreate a perfect environment for their program and save you LOADS of hassle trying to set it up.

The benefit of all this is that you can know exactly where application state is stored, know that you're running the app in it's right environment, and it becomes turbo easy to install updates, or roll back if needed.

Totally spin up a VM, install docker on it, and deploy 2-3 web apps. You'll notice that you use the same way of configuring them, starting and stopping them, and you might not want to look back ;)

The most popular way of configuring containers are by using environment variables that live outside the container. But for apps that use files to store configuration, you can designate directories on your host that will be available inside the container (called "volumes" in Docker land). It's also possible to link multiple containers together, so you can have a database container running alongside the app.

Just until they kill it as well

Of course

Obviously it means that it you want to open a restaurant, you have to own a bike first

I cannot unsee this like he has a dummy

I generally feel fine if I can preview the payload and it doesn't contain too identifiable stuff. Even better if you can redact fields. NewPipe has a simple implementation of this where it just opens up your email client with a pre-filled body.

Not if they don't track you. As far as I understand the fabled cookie law, you only need to have that notice if you're using cookies in a way that's not strictly necessary for the site's functionality.

My coworker had this issue recently, and he had to screw around with different cables, docks, and profile settings on the monitor itself for half an hour before the better refresh rates showed up

Set your default browser to another one, then it should be clickable again