3 ms·

It's not just this. Developer relations have gone to shit and visual studio on large projects like ours (2mloc c#) is a liability. Oh and add the schizophrenic

It's not just this. Developer relations have gone to shit and visual studio on large projects like ours (2mloc c#) is a liability. Oh and add the schizophrenic nature of devdiv and it's just not worth it anymore. Need we say more: SQL licensing, Silverlight, windows workflow rewrite, EF is a piece of shit, MS11-100 (demon hotfix from hell). I could go on for days. We have blown over 24 days in the last 2 years on just phone calls to Microsoft. We threw out partnership agreement in last year (we were gold). Not going near Mono. It's another ghetto. To be honest, our front end is going to python and the back end to postgres. Any critical sections go to C++.

MichaelGG 13y ago
So long it's not a the grass-is-greener effect. While I'm not pleased with a lot of Microsoft's recent developments, and C# seems to be an evolutionary dead-end, it's not like other platforms are beautiful. I'm sure there are lots of shit frameworks like EF on other platforms; it's not like EF is some critical piece of .NET. Personally, F# is the number one reason I'm still on .NET, with VS being a very strong second place. I've had critical telecom services running on Mono for many years; not sure what "ghetto" means there. Xamarin also seems to be doing quite well with their cross-platform initiatives. I've moved SQL Server apps to Postgres (due to licensing) and back (due to maintenance/replication). On another we're moving to PG again due to licensing. Postgres is great, but holy shit MSSQL provides a huge feature surface that's very accessible (licensing aside). SSMS is a dream compared to the ghetto of PG frontends (in my limited experience). But if you can easily dump and rewrite, I'll admit, that is fun.