Add Windows instructions

[aninrusimha]

Either add instructions for python venv or WSL

[robertquitt]

Arent the instructions the same for windows? What specifically needs to be added?

[aninrusimha]

The action of venv is different apparently. Also I want to link to WSL because its great

[robertquitt]

WSL was a cool idea but doesnt work, and WSL2 is just a glorified VM... whats so good about it?

[aninrusimha]

WSL2 is a glorified VM that is surprisingly lightweight and has a lot of good features/integrations out of the box, such as being able to access all Ubuntu / Windows files from each other with ease. The other vm/bash options haven't worked nearly as well

[toulouse]

Taken to the logical extreme:
Docker is just a glorified cgroups, What's so good about it?
cgroups is just a glorified chroot jail with extra configuration. What's so good about it?
chroot jails are just a glorified filesystem with optimizations. What's so good about it?
filesystems are just glorified kernel modules with filesystem access.

A real, non-sarcastic answer:
It offers immutable, pre-packaged kernels which easily and efficiently unpack into an accessible Linux system complete with networking and even filesystem access (\\wsl$\) built in, preconfigured and ready to run applications on top of.

It is important to remember to evaluate the merits of something not merely by its components, but also its impact and value to those using it. A uniform, lightweight, and compatible target that enables developer use cases is highly useful and not worth dismissing on the grounds that it is an effective combination of boring tech.

[toulouse]

Ultimately, efforts to support bootstrapping developers tend to pay dividends, so long as the use case is not seen as outlandish or otherwise difficult to support. While WSL should be as transparent as possible, there is a case tot be made that any custom setup could be briefly noted; a simple suggestion of "to run this on Windows, it is recommended to use WSL. Linux development is tested and deployed primarily on " (i.e. Ubuntu, Debian, Fedora, CentOS, etc with version numbers).

[robertquitt]

It offers immutable, pre-packaged kernels which easily and efficiently unpack into an accessible Linux system complete with networking and even filesystem access (\wsl$) built in, preconfigured and ready to run applications on top of.

Good to know! I had a terrible experience working with WSL and I haven't worked with WSL2, so I wasn't really on board with it. Thanks for your input!

While WSL should be as transparent as possible, there is a case tot be made that any custom setup could be briefly noted; a simple suggestion of "to run this on Windows, it is recommended to use WSL. Linux development is tested and deployed primarily on " (i.e. Ubuntu, Debian, Fedora, CentOS, etc with version numbers).

Makes sense

The action of venv is different apparently.

I haven't run through the set up on windows, I have been using my personal Ubuntu 16.04 server. I'm not aware of those
differences. When I used windows before, I think I just installed everything to the systemwide PYTHONPATH and used git bash lol

Somewhat related--instructions I might add is IDE/editor setup. Personally, I use Vim with a black autoformat script and tmux. I autoindented the django html templates by sending them through Vim as well lol. I know VS Code is popular with the kids these days, might be worth adding any setup steps there (if any).