> Um the dependency hell is not something I have seen in Windows, but quiet often in Linux.
You never had to install 2 different version of php with IIS. My worst internship by far, it took us almost 3 week to get my workstation to work, and my coworkers were windows powerusers. I'd rather spend multiple times 10 minutes to resolve dependency hell than spend again 3*40 hours doing the same thing, just with no understnding of what i'm doing.
If you stick to the distro package manager you should never see dependency hell on linux, in 15+ years of using it I've seen it three times. Once was when I was being too clever for my own good with the package manager, once was from using third part package managers (ruby gems) and once is from co-workers essentially creating their own distro + package manager on top of red hat ( a story in it's own right). The root cause of each of those was ignoring or screwing with the package manager. And the last two started out as deficiencies (non-existence) in windows package management.
On windows I've come across it much more. Installing different versions of Visual Studio, installing some random program that doesn't package it's binaries, various installers including sub-installers, trying to run a program that requires the .net framework and having to install that first.
I spent most of this morning dealing with a windows app that was missing a dll and had to google my way through with lot's of trial and error to find the missing package.
I've also had docker for windows screw up my cygwin install, but I guess that's a point in each column.
You never had to install 2 different version of php with IIS. My worst internship by far, it took us almost 3 week to get my workstation to work, and my coworkers were windows powerusers. I'd rather spend multiple times 10 minutes to resolve dependency hell than spend again 3*40 hours doing the same thing, just with no understnding of what i'm doing.