3 ms·

C# and .Net was for a very long time a Windows only thing, they were created to fight against Java so Microsoft can keep selling Windows licenses. IMO this Mic

C# and .Net was for a very long time a Windows only thing, they were created to fight against Java so Microsoft can keep selling Windows licenses. IMO this Microsoft stupidity to not open source .Net and FUD the open source alternatives costed them and the entire dev community a lot, we would have a good alternative for cross platform high level languages with a big framework (as alternative to JS+node+electron+npm+framewoks)

pjmlp 5y ago
First class languages for the Windows Platform.
- simion314 5y ago
  Sure, but they linked a good dev platform with an OS, this prevented .Net to become a much more used platform because most developers developed for Linux server using anything else then .Net (java,PHP,Python or the super shitty at that time JS and node). The open source community might have implemented an open alternative but only some parts of the language and platforms were open and there was a lot of fear that Mono that implemented some non open API could be a liability. I personally was a big fan of C# and I can't forgive MS stupidity , because of the Windows Team a good language and platform was sabotaged, as I said it could have been a worthy competitor to JS/node especially in the past when JS was shit and even now where npm is filled with leftPads and colorRed packages.
  - viraptor 5y ago
    They're pushing hard in that direction with https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blaz... I don't think we've heard the last word yet.
  - pjmlp 5y ago
    JS/node are no competitors to .NET, not even close, only in the minds of script kiddies.
    - simion314 5y ago
      I only done desktop .Net apps so I can't judge, but even if I love the language and the standard library in .Net I would never had considered using it on a server if I had a choice, not because of quality but because of Microsoft bad treatment of the licenses an, the FUD and how they handled it. They managed to drag this platform down that js and node has probably more users and mind-share, they even had to "port "C#" and create TypeScript. Btw, i did not implied anything about node or npm quality, someone that worked with both seriously in recent years might add their thoughts (so I am not a node fan just a C# lower disappointed on MS behavior).

pjmlp 5y ago

First class languages for the Windows Platform.

simion314 5y ago
Sure, but they linked a good dev platform with an OS, this prevented .Net to become a much more used platform because most developers developed for Linux server using anything else then .Net (java,PHP,Python or the super shitty at that time JS and node). The open source community might have implemented an open alternative but only some parts of the language and platforms were open and there was a lot of fear that Mono that implemented some non open API could be a liability. I personally was a big fan of C# and I can't forgive MS stupidity , because of the Windows Team a good language and platform was sabotaged, as I said it could have been a worthy competitor to JS/node especially in the past when JS was shit and even now where npm is filled with leftPads and colorRed packages.
- viraptor 5y ago
  They're pushing hard in that direction with https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blaz... I don't think we've heard the last word yet.
- pjmlp 5y ago
  JS/node are no competitors to .NET, not even close, only in the minds of script kiddies.
  - simion314 5y ago
    I only done desktop .Net apps so I can't judge, but even if I love the language and the standard library in .Net I would never had considered using it on a server if I had a choice, not because of quality but because of Microsoft bad treatment of the licenses an, the FUD and how they handled it. They managed to drag this platform down that js and node has probably more users and mind-share, they even had to "port "C#" and create TypeScript. Btw, i did not implied anything about node or npm quality, someone that worked with both seriously in recent years might add their thoughts (so I am not a node fan just a C# lower disappointed on MS behavior).