That is because windows filesystem is mounted to WSL through NFS and while transferring large files through that is ok, transferring huge amounts of small files is really slow.

Better in which way? WSL2 is a VM running ALONGSIDE Windows, not inside. Its performance is basically bare metal. If you have enough RAM, there is no reason to use cygwin instead of WSL2.

Learn it first.

I almost exclusively use it with my own Dockerfiles, which gives me the same flexibility I would have by just using VM, with all the benefits of being containerized and reproducible. The exceptions are images of utility stuff, like databases, reverse proxy (I use caddy btw) etc.

Without docker, hosting everything was a mess. After a month I would forget about important things I did, and if I had to do that again, I would need to basically relearn what I found out then.

If you write a Dockerfile, every configuration you did is either reflected by the bash command or adding files from the project directory to the image. You can just look at the Dockerfile and see all the configurations made to base Debian image.

Additionally with docker-compose you can use multiple containers per project with proper networking and DNS resolution between containers by their service names. Quite useful if your project sets up a few different services that communicate with each other.

Thanks to that it’s trivial to host multiple projects using for example different PHP versions for each of them.

And I haven’t even mentioned yet the best thing about docker - if you’re a developer, you can be sure that the app will run exactly the same on your machine and on the server. You can have development versions of images that extend the production image by using Dockerfile stages. You can develop a dev version with full debug/tooling support and then use a clean prod image on the server.

English is not my first not language. When I write something down in my first language (polish), it feels more like I’m transcribing things I silently say to myself, while with english I’m actually thinking about every word I type.

The funny thing is, the better I am getting at English, making those types of mistakes is getting easier for me.

But idk, this is just my experience.

Because they learned that from hearing, not reading so that makes sense.

Seems like CPU-intensive game, so it makes sense.

Simple fails when complex problem arrives. Declarative approach of systemd daemons allows for more versatile solutions in unified format.

Not only OS - written using 3D APIs closed source available only for your OS.

Actually “natural” gets a pass from me. It doesn’t feel right just because we got used to the opposite.

Imagine a paper scroll on rolls. If you slide the top of the roll upwards - the paper goes up, and you can see more bottom content. The exact opposite happens when you scroll the mouse wheel with default config.

Is SMTP out of question?

It is better than in most languages with exceptions, except from languages like Java, that require you to declare that certain method throws certain error.

It’s more tedious in Go, but at the end of the day it’s the same thing.

When I use someone else’s code I want to be sure if that thing can throw an error so I can decide what to do with it.

Distrobox, docker, flatpaks and other containerized solutions?

Yup, if you have SSH service open on port 22, you’re automatically spammed by bots trying to brute force their way onto the system.

AFAIK it’s now 100, so basically unlimited for personal use.