4 ms·
Having recently moved to Visual Studio 2015, I can't say I agree. Especially compared to something like PyCharm with Django. Visual Studio wasn't too bad (Ok, i
by jenkstom 10y ago
Having recently moved to Visual Studio 2015, I can't say I agree. Especially compared to something like PyCharm with Django. Visual Studio wasn't too bad (Ok, it really was for an installer), but getting up to speed is just a nightmare. I've been trying to get identity to work on PostgreSQL for weeks, where it "just works" in Django.
Granted, if I completely stuck with the Microsoft stack I wouldn't have this problem. But if I stuck with the Microsoft stack I'd be deploying Silverlight apps too...
Microsoft is making efforts with .net core to move past the infamous lock-in effect. But they aren't there yet.
Don't get me wrong, I write an awful lot of c# code. But I write a lot of extra code making things work that should be easy. Ever tried to integrate Entity Framework into an IBM iSeries? If you figure that out, please let me know. Please let everybody know.
- herbst 10y agoIt was more ment as a joke, there is nothing in this world so complicated to setup like any dev stack on windows. They must hate developers so much its kind of sad.
- kamau 10y agoWould it have been easier if you had tried to make Django talk to SQL Server or Active Directory? In other words is this just the MS stack making things difficult for you or just a general impedance mismatch of tools that weren't designed with each other in mind?