3 ms·
The comments in this thread are mostly valid, but are actually skipping over several more fundamental mistakes that the author of the article is making. From th
by jiggawatts 4y ago
The comments in this thread are mostly valid, but are actually skipping over several more fundamental mistakes that the author of the article is making. From the sounds of it, he's multi-booting an entire physical machine into Windows, which is the wrong workflow to use in 2022 as a developer! (He mentions being forced to copy the files out to a USB stick.)
In case it's not obvious (it wasn't obvious for the article author) my recommendations for scenarios like this are:
- Use virtual machines. The benefits here are that you don't have to do horrible things to your disk partitions, you can use snapshots and roll back to them, and you can have many OS versions running in parallel for testing. More importantly, even if catching up with patches took 90 minutes, you can let a virtual machine do that in the background instead of locking up your entire PC as in traditional multi-booting.
- Use cloud-hosted virtual machines. Same benefits as the above, but without taking up disk space locally. Especially useful if you have multiple computers and you like to shift between them. There are generous free tiers available in both AWS and Azure. Both provide up-to-date base images for VMs that take about 2 minutes to deploy instead of 90 minutes. Deploying an image and installing Visual Studio from scratch would take less than 90 minutes!
- Use Azure DevOps Pipelines or GitHub Actions. Both have free tiers and let you run automated builds using Windows-based runner images maintained by Microsoft. They're always up-to-date with patches, Visual Studio updates, and various related tools. This is the superior option for building packages of things where you don't need a fast edit-build-test cycle.
- teclordphrack2 4y ago