How to make Windows a proper development environment

Here’s an article to reassure Windows developers who feel their
platform is increasingly being overshadowed by Linux these days: how
to set up a nice Windows development environment
<https://www.infoworld.com/article/4196853/how-to-make-windows-a-proper-development-environment.html>.

Step 1: Install Linux. Not even kidding: install WSL, so you get
access to a Linux system while still being able to pretend that you’re
using Windows.

Step 2: Admit that the native Windows filesystem, NTFS, doesn’t deal
well with lots of files and directories, like Linux filesystems can.
Install something called “ReFS”, which Microsoft was pushing quite
heavily at one point, but now seems to have lost a lot of its
enthusiasm for. Don’t worry, I’m sure Microsoft’s layoffs haven’t
reached the team working on that -- yet.

Step 3: Try doing Windows software installs the Linux way, with
Microsoft’s Linux-wannabe package manager, WinGet. Only it doesn’t
quite work like a Linux package manager: it won’t install packages by
name, you have to use those arcane ID strings instead. Good luck
figuring those out.

Step 4: Enable PowerShell to run local scripts without proper checks.
What could possibly go wrong? Linux, being a multiuser system, has
built-in protection checks; but who needs that kind of stuff on
Windows?

Step 5: Install more and more tools from the Linux world. Isn’t it
reassuring when recommended package manager commands use options like
“--force” and “--override” in them? I’m sure it’ll all work out fine
without those extra checks, you can trust Microsoft!

And there you have it: a proper, pukka Windows-native development
environment for creating Windows-native software, which can hold its
head up high next to any Linux machine!