4 ms·

Their license for the .NET Core debugger makes it so that only they can use it, JetBrains and others cannot, see [1], they haven't changed at all. 1 - https://

Their license for the .NET Core debugger makes it so that only they can use it, JetBrains and others cannot, see [1], they haven't changed at all. 1 - https://blog.jetbrains.com/dotnet/2017/02/15/rider-eap-17-nuget-unit-testing-build-debugging https://blog.jetbrains.com/dotnet/2017/02/15/rider-eap-17-nu...

Dayshine 8y ago
My understanding is that the debugger is an adapted version of the closed source Visual Studio debugger. Visual Studio isn't open source, and is a paid for product. It takes time to break things out from inside a larger closed source project...
- dmarlow 8y ago
  Some editions are, I suppose. For many things VS Community is free though.
  - slrz 8y ago
    I don't think any editions of Visual Studio are available as Open Source software. The Community thingie is gratis but doesn't come with source code. There's VSCode (is that OSS?) but that's not an edition of VS but rather a whole different product.
    - sulam 8y ago
      VSCode is absolutely OSS.
efdee 8y ago
Why would Microsoft give away their crown jewels to a competing IDE? They spent ages perfecting their debugger. It's not like JetBrains can't build their own debugger based on the ICorDebug interface (which is what Microsoft's implementation is also based on).
- contravariant 8y ago
  Nobody here is claiming proprietary code is inherently bad (some people definitely do, but not in this thread), they're just saying it makes a poor example of Microsoft embracing open source.
  - Someone1234 8y ago
    JetBrains products aren't Open Source. So how is embracing a closed source for-profit company anything to do with embracing Open Source?
    - contravariant 8y ago
      You're asking why releasing an open source debugger has anything to do with embracing open source because there are closed source companies that are also making a debugger?
      - Someone1234 8y ago
        > You're asking why releasing an open source debugger has anything to do with embracing open source I don't even understand what that means. It was never Open Source, it was part of the IDE(s). Microsoft released an update package for their IDE(s) on NuGet which JetBrains used before their native debugger was ready. If Microsoft are to be shamed for keeping their IDE's debugger closed source then JetBrains should be equally shamed, both have closed source proprietary IDEs.
    - AsyncAwait 8y ago
      > how is embracing a closed source for-profit company anything to do with embracing Open Source? Truly embracing open-source with .NET core would mean that, yes, even a proprietary product could make use of it. A debugger is extremely core to having a language being open-source and artificially limiting it to your own products is the exact opposite of 'embrace' Also, JetBrains does have an open-source debugger in their community versions, but this is not what the debate is about.

Dayshine 8y ago

My understanding is that the debugger is an adapted version of the closed source Visual Studio debugger. Visual Studio isn't open source, and is a paid for product. It takes time to break things out from inside a larger closed source project...

dmarlow 8y ago
Some editions are, I suppose. For many things VS Community is free though.
- slrz 8y ago
  I don't think any editions of Visual Studio are available as Open Source software. The Community thingie is gratis but doesn't come with source code. There's VSCode (is that OSS?) but that's not an edition of VS but rather a whole different product.
  - sulam 8y ago
    VSCode is absolutely OSS.

efdee 8y ago

Why would Microsoft give away their crown jewels to a competing IDE? They spent ages perfecting their debugger. It's not like JetBrains can't build their own debugger based on the ICorDebug interface (which is what Microsoft's implementation is also based on).

contravariant 8y ago
Nobody here is claiming proprietary code is inherently bad (some people definitely do, but not in this thread), they're just saying it makes a poor example of Microsoft embracing open source.
- Someone1234 8y ago
  JetBrains products aren't Open Source. So how is embracing a closed source for-profit company anything to do with embracing Open Source?
  - contravariant 8y ago
    You're asking why releasing an open source debugger has anything to do with embracing open source because there are closed source companies that are also making a debugger?
    - Someone1234 8y ago
      > You're asking why releasing an open source debugger has anything to do with embracing open source I don't even understand what that means. It was never Open Source, it was part of the IDE(s). Microsoft released an update package for their IDE(s) on NuGet which JetBrains used before their native debugger was ready. If Microsoft are to be shamed for keeping their IDE's debugger closed source then JetBrains should be equally shamed, both have closed source proprietary IDEs.
  - AsyncAwait 8y ago
    > how is embracing a closed source for-profit company anything to do with embracing Open Source? Truly embracing open-source with .NET core would mean that, yes, even a proprietary product could make use of it. A debugger is extremely core to having a language being open-source and artificially limiting it to your own products is the exact opposite of 'embrace' Also, JetBrains does have an open-source debugger in their community versions, but this is not what the debate is about.