core

Well, if not Mono, then the .NET Core runtime package, right? It's not self-contained. I read this [1], but it's unclear to me how I build a self-contained binary, or what options are available for AOT. [1] https://github.com/dotnet/core/blob/master/Documentation/sel...

It's not without precedent! With .NET Core [0], and ChakraCore[1] (Edge's JS engine) both being open sourced. And them having thrown the entirety of MS-DOS [2] up under the MIT license, and making a bunch of new tools and stuff under open licenses (VSCode, TypeScript, msbuild, etc...). I honestly wouldn't be surprised if they started making a push to open up many parts of Windows. Already some devs on the Edge team have said publicly that they are working on open sourcing the whole rendering engine from Edge, and seeing that they are moving toward having Windows be more of a "platform" and less of "software you buy", it makes sense that it could eventually become an open source (or at least "open core") product. I don't think it will happen this year, but I do think that if MS keeps going in this direction, it's more likely than not to ha

For what it's worth, the IlLinker can get Hello World down to 20MB and as many files: https://github.com/dotnet/core/blob/master/samples/linker-in... If you use some extra options to disable crossgen and link System.Private.CoreLib, you can get the size down to 10MB, at the expense of startup time: https://github.com/AustinWise/IlLinkerExample

Jetbrains was using a package provided by Microsoft and blogged that they would soon have to disable debugging of CoreCLR Read “The Bad News” https://blog.jetbrains.com/dotnet/2017/02/15/rider-eap-17-nu... Also the licensing issue https://github.com/dotnet/core/issues/505 Then a week later with the licensing issue still in place Jetbrains implemented their own debugger, on the comments it reads "This is our own debugger implementation." https://blog.jetbrains.com/dotnet/2017/02/23/rider-eap-18-co...

It's very frustrating having all of these tools only support Windows. Despite all the wonderful work Microsoft has done with CoreCLR, the "IDE" debugger is still only available under a license that only permits use with Visual Studio and VSCode [1] and mdbg is still nowhere to be found for CoreCLR [2]. 1: https://github.com/dotnet/core/issues/505 2: https://github.com/dotnet/coreclr/issues/1145 From what I've gathered, the best you have right now for doing command line debugging is the "SOS" plugin for lldb, which seems to require building the lldb plugin and sometimes even lldb (!!) yourself [3][4]. 3: https://github.com/dotnet/coreclr/blob/master/Documentation/... 4: http://blogs.microsoft.co.il/sasha/2017/02/26/analyzing-a-ne... Not very fun if you're not using Windows.