> 1. The Dev environment is basically superior to everyone else's now.
I've done "Windows" development for about half of my 20-year career, and PHP/Rails for the other half. (It's all mixed together; I'm talking about overall effort.) My job, for the past 2 years, has been 100% Visual Basic .NET. (Personal projects continue in Rails.) I'm sick to death with it, and eagerly await a side gig in Rails and OS X, which should lead to a massive side project in Java. I can't wait. I'll take development on OS X and Linux every day of the week and twice on Sunday over Windows and Visual Studio. Some days, like today, I don't know what I was thinking taking this job.
I guess it all comes down to personal preference, but today was a perfect example. 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.
And I mostly HATE IntelliSense, always popping up and covering what I'm trying to type, and Visual Studio's stubborn way of screwing up my code with its auto-completion of IF statements. Yet I leave it on, for the 5% of the time I want to actually use it.
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. (So I do that work on my home PC.) And they run their own DNS system, which doesn't know that about half the internet exists. Oh, and the proxy has recently started killing my application for one user at random. No, these aren't Windows or Visual Studio's problems, but these SORTS of problems are frequently part of a "Windows development ecosystem" found in large companies that pay a lot of money to rubbish consultancies.
> 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.
I've done "Windows" development for about half of my 20-year career, and PHP/Rails for the other half. (It's all mixed together; I'm talking about overall effort.) My job, for the past 2 years, has been 100% Visual Basic .NET. (Personal projects continue in Rails.) I'm sick to death with it, and eagerly await a side gig in Rails and OS X, which should lead to a massive side project in Java. I can't wait. I'll take development on OS X and Linux every day of the week and twice on Sunday over Windows and Visual Studio. Some days, like today, I don't know what I was thinking taking this job.
I guess it all comes down to personal preference, but today was a perfect example. 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.
And I mostly HATE IntelliSense, always popping up and covering what I'm trying to type, and Visual Studio's stubborn way of screwing up my code with its auto-completion of IF statements. Yet I leave it on, for the 5% of the time I want to actually use it.
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. (So I do that work on my home PC.) And they run their own DNS system, which doesn't know that about half the internet exists. Oh, and the proxy has recently started killing my application for one user at random. No, these aren't Windows or Visual Studio's problems, but these SORTS of problems are frequently part of a "Windows development ecosystem" found in large companies that pay a lot of money to rubbish consultancies.
I know, I know. Horses for courses.