I miss the days of being a Microsoft dev where your choices were clear cut.
Dustin Briscoe

I was a .NET developer and I think you’re romanticizing Microsoft/Apple environments a lot. ASP.NET development was reasonably straightforward, but the tooling was very limited and often shoehorned your app into working a certain way. I can still spot that an app is ASP.NET by looking at it because it offered so little flexibility. Also, part of why it was comfortable was because it moved very slow compared to the speed of innovation that we have now. There is a reason why most software shops have moved away from Microsoft — they were just too slow and closed. And don’t get me started on SharePoint.

It also baffles me that you think that Apple has great developer tooling. I really don’t understand how you could possibly think this. Swift is a pretty nice language, but it changes WAY more than JavaScript does, and Objective-C is what you in practice will have to deal with for years to come, and it’s truly atrocious, and XCode is a very sad development environment compared to Visual Studio or IntelliJ. It also lacks a standard (or even defacto standard) package manager, which is something I would expect from a centralized ecosystem like Apple. And don’t get me started on the madness of provisioning profiles — I’ll take webpack troubles any day.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.