5 ms·

I'm not sure anyone who truly cares about effort uses .net core. :p I mean, it's a cheap shot, but it's frankly so unproductive compared to Django it's basical

I'm not sure anyone who truly cares about effort uses .net core. :p I mean, it's a cheap shot, but it's frankly so unproductive compared to Django it's basically a running joke. Not that .net core doesn't see a lot of usage, much like angular it's very popular in the european public sector, but it's just such a waste of resources. By resources I mean, man hours by the way, because it's really effective technically, it's just that, all that you can pay for around a million years of AWS/Azure time for the extra wage-hours you need to pay programmers when you use .net instead of something useful. And in two years it'll be obsolete anyway, because by then Microsoft will have completely changed their direction, again. I say this, as as someone who's running Azure and 365 as our cloud provider for the majority of our services, as someone who's genuinely happy with the services Microsoft provides and having had a great 25 year long business relationship with them, but as far as development goes, .net is just too crazy to be worth it these years.

elboru 8y ago
> And in two years it'll be obsolete anyway, because by then Microsoft will have completely changed their direction, again. You could say the same about the whole industry, also I don't think "obsolete" is a good term, maybe some technologies are not the "new shining thing" out there, but well written systems with "old" and "uncool" technologies are still working perfectly fine and they will keep working fine in the future.
zamalek 8y ago
> frankly so unproductive compared to Django Django is at a completely different abstraction layer.
GordonS 8y ago
I actually love working with .NET Core, and I'm really productive with C#. For some background, I'm pretty much a polyglot; while C# is where I spend most of my time, I also regularly work with JavaScript and Typescript, and occasionally with Java, PHP and C. I also find it preposterous that .NET Core will be obsolete in 2 years, and I'm not sure what you mean about Microsoft changing direction "again" - the .NET Framework was released almost 2 decades ago, and I find the recent move to a cross-platform runtime to make for exciting times!
- AchieveLife 8y ago
  Have you tried the SAFE stack with .Net core? https://safe-stack.github.io/ https://safe-stack.github.io/
  - GordonS 8y ago
    I haven't, but it looks really interesting! I've only dabbled with F#, but I always enjoyed it when I do - I just wish I could find the time to spend on it :(
- eksemplar 8y ago
  Really? Because stuff like silverlight, linq_to_sql, razor/mvc and others might want a word. I know technology moves forward, by typically it does so in a much less costly manner, because in the real world, moving people from asp.net classic to .net core costs money. I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0.
  - GordonS 8y ago
    > silverlight Hah, I forgot about Silverlight - mainly because I never used it (did anyone?) > razor/mvc Eh? Razor is very much still alive, and MVC lives on as ASP.NET Core MVC. > because in the real world, moving people from asp.net classic to .net core costs money. Yes, I live in the same world, and have migrated several projects from .NET to .NET Core. If you were an early adopter, it could admittedly be a bit painful, but everything "just works" now. > I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0. Really not sure what you mean here, and I can only guess that you've been thrown by Microsoft randomly releasing new .NET Core versions before the corresponding .NET Standard versions - releasing the implementation before the API. I don't like this myself, but it hardly means that .NET Standard has "came and went". Also, just a couple of weeks ago, Microsoft said ".NET Core 3.0 as well as upcoming versions of Xamarin, Mono, and Unity will be updated to implement .NET Standard 2.1"[1]. [1] https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcing-net-standard-2-1/ https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcin...
bobblywobbles 8y ago
django is rank 253 on the fortunes benchmark (https://www.techempower.com/benchmarks/ https://www.techempower.com/benchmarks/), .net core is rank 6. I feel .net core is productive to django, but I don't like using python so my opinion is bias.
- eksemplar 8y ago
  When I say productive, I'm talking about time to market. I don't really care about the efficiency because iron is cheap and development time is not.

elboru 8y ago

> And in two years it'll be obsolete anyway, because by then Microsoft will have completely changed their direction, again. You could say the same about the whole industry, also I don't think "obsolete" is a good term, maybe some technologies are not the "new shining thing" out there, but well written systems with "old" and "uncool" technologies are still working perfectly fine and they will keep working fine in the future.

zamalek 8y ago

> frankly so unproductive compared to Django Django is at a completely different abstraction layer.

GordonS 8y ago

I actually love working with .NET Core, and I'm really productive with C#. For some background, I'm pretty much a polyglot; while C# is where I spend most of my time, I also regularly work with JavaScript and Typescript, and occasionally with Java, PHP and C. I also find it preposterous that .NET Core will be obsolete in 2 years, and I'm not sure what you mean about Microsoft changing direction "again" - the .NET Framework was released almost 2 decades ago, and I find the recent move to a cross-platform runtime to make for exciting times!

AchieveLife 8y ago
Have you tried the SAFE stack with .Net core? https://safe-stack.github.io/ https://safe-stack.github.io/
- GordonS 8y ago
  I haven't, but it looks really interesting! I've only dabbled with F#, but I always enjoyed it when I do - I just wish I could find the time to spend on it :(
eksemplar 8y ago
Really? Because stuff like silverlight, linq_to_sql, razor/mvc and others might want a word. I know technology moves forward, by typically it does so in a much less costly manner, because in the real world, moving people from asp.net classic to .net core costs money. I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0.
- GordonS 8y ago
  > silverlight Hah, I forgot about Silverlight - mainly because I never used it (did anyone?) > razor/mvc Eh? Razor is very much still alive, and MVC lives on as ASP.NET Core MVC. > because in the real world, moving people from asp.net classic to .net core costs money. Yes, I live in the same world, and have migrated several projects from .NET to .NET Core. If you were an early adopter, it could admittedly be a bit painful, but everything "just works" now. > I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0. Really not sure what you mean here, and I can only guess that you've been thrown by Microsoft randomly releasing new .NET Core versions before the corresponding .NET Standard versions - releasing the implementation before the API. I don't like this myself, but it hardly means that .NET Standard has "came and went". Also, just a couple of weeks ago, Microsoft said ".NET Core 3.0 as well as upcoming versions of Xamarin, Mono, and Unity will be updated to implement .NET Standard 2.1"[1]. [1] https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcing-net-standard-2-1/ https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcin...

bobblywobbles 8y ago

django is rank 253 on the fortunes benchmark (https://www.techempower.com/benchmarks/ https://www.techempower.com/benchmarks/), .net core is rank 6. I feel .net core is productive to django, but I don't like using python so my opinion is bias.

eksemplar 8y ago
When I say productive, I'm talking about time to market. I don't really care about the efficiency because iron is cheap and development time is not.