> I spent half the day fighting updating packages with NuGet, from one machine to another, and a sudden incompatibility with Azure database exports with my local version. Sure, there are problems with every dev environment, but it just seems so much MORE of a hassle with Visual Studio on Windows, since, for all their money and effort and marketing and the fact that they own the whole stack, the pain ought to be much LESS than the alternatives.
Well I mean... I could tell you my java/maven nightmare stories as well. Dependency hell is not something anyone gets to escape, even if you're using newer hotness like NPM or Go. Oh god, Go's dependency management is a trap.
> It also doesn't help that my Fortune 150 IT department has my development machine so locked down that the Azure worker simulator literally cannot get the permissions it needs to run.
There is no escape for us, except to burn our way out.
Well I mean... I could tell you my java/maven nightmare stories as well. Dependency hell is not something anyone gets to escape, even if you're using newer hotness like NPM or Go. Oh god, Go's dependency management is a trap.
> It also doesn't help that my Fortune 150 IT department has my development machine so locked down that the Azure worker simulator literally cannot get the permissions it needs to run.
There is no escape for us, except to burn our way out.