3 ms·

I know what you mean :-) Incidentally the Windows-only days will one day be a memory: https://get.asp.net/ https://get.asp.net/

scruple 11y ago
Yeah, well, I've been hearing the "one-day we'll be on Linux" claims long enough to grow tired and move on. Developing on Windows, after having had some experience developing in a Linux/Mac environment, feels like second class citizenry. That's without even talking about nuget, etc...
- manigandham 11y ago
  .NET has been available on Linux for years via Mono (with various compatibility issues but it works). And the next official version with cross platform support already has a Go Live license which means Microsoft will support any production app. "one-day" is today.
  - scruple 11y ago
    What production application are you deploying in .NET on Linux today? edit/ I'm not letting you off this easily. Mono never really worked and never really had Microsoft's support. Where's the ecosystem?
    - manigandham 11y ago
      We have some smaller backend stuff running today (messaging, logging, etc). Bigger apps have dependencies that are still waiting to be compatible with .NET Core.
    - manigandham 11y ago
      In reply to your edit: Yes, Mono had issues as I said but it did/does work if you can work around it. Granted the windows licenses are cheaper than the dev effort to fix any potential issues so it's not the best situation. But .NET Core can be used today and it works fine with the framework rapidly being developed. Several major libraries are also in or have completed the migration and we're just waiting on some other dependencies but we do have smaller apps running today. Ecosystem for the code is the same (and as vast) as it's ever been, that's the strength of the CLR/framework. Mono/.net on linux does have a community but it's growing quickly now with Core.

3 ms·

I know what you mean :-) Incidentally the Windows-only days will one day be a memory: https://get.asp.net/ https://get.asp.net/

by johnny_reilly 11y ago

scruple 11y ago
Yeah, well, I've been hearing the "one-day we'll be on Linux" claims long enough to grow tired and move on. Developing on Windows, after having had some experience developing in a Linux/Mac environment, feels like second class citizenry. That's without even talking about nuget, etc...
- manigandham 11y ago
  .NET has been available on Linux for years via Mono (with various compatibility issues but it works). And the next official version with cross platform support already has a Go Live license which means Microsoft will support any production app. "one-day" is today.
  - scruple 11y ago
    What production application are you deploying in .NET on Linux today? edit/ I'm not letting you off this easily. Mono never really worked and never really had Microsoft's support. Where's the ecosystem?
    - manigandham 11y ago
      We have some smaller backend stuff running today (messaging, logging, etc). Bigger apps have dependencies that are still waiting to be compatible with .NET Core.
    - manigandham 11y ago
      In reply to your edit: Yes, Mono had issues as I said but it did/does work if you can work around it. Granted the windows licenses are cheaper than the dev effort to fix any potential issues so it's not the best situation. But .NET Core can be used today and it works fine with the framework rapidly being developed. Several major libraries are also in or have completed the migration and we're just waiting on some other dependencies but we do have smaller apps running today. Ecosystem for the code is the same (and as vast) as it's ever been, that's the strength of the CLR/framework. Mono/.net on linux does have a community but it's growing quickly now with Core.