[mjsabby]

Folks, adding mscorlib binary compatibility is not going to boil the ocean or alter the "Core"-ness of .NET Core.

I implore you to take a look at this pull request:

https://github.com/dotnet/coreclr/pull/4874

All this does is changes the "core" library for CoreCLR to be renamed from "mscorlib" to "System.Private.Corelib" -- this has an important function, now the .NET team can add more backward compat features (missing types and methods) to mscorlib for those who want to use it.

If your library or product doesn't want to use it, you don't need to.

.NET Core doesn't become more bloated, it says beautiful and Core.

[j_s]

If you want to point out specific issues as a positive for the future of .NET Core (and that looks like a good one), it's only fair to include ones showing the negatives right now. This is why the best answer at the moment is "wait and see":

https://github.com/JamesNK/Newtonsoft.Json/issues/618

Muddling around, guessing by looking at what other people have done and discovery by word of mouth through the community sucks.