The second sentence on the page you linked literally says

"It has been heavily inspired by the excellent Rich library for Python written by Will McGugan."

:)

Ah yes didn't see that at first, thanks!

Visual Studio 2017 15.6 shipped a new feature called "Navigate to Decompiled Sources" in March.

> First is that MSBuild hard-codes references, so building a multi-targeted project with references to a multi-targeted NuGet package is a nightmare. From what I've read in the documentation, Paket (an alternative package manager) is supposed to be designed to help with this, but it was already enough of a struggle to introduce NuGet at my work, and NuGet is "built-in" to Visual Studio.

This has changed radically with Visual Studio 2017 and the newer MSBuild tooling. See https://github.com/khellang/Scrutor/blob/master/src/Scrutor/... for an example. It has three targets with both conditional and common package references.

Fun Fact: VS Code started life in Azure as Project Monaco. It was later pulled into an Electron app and released as VS Code :)

This gist by @davidfowl might make the relationship between the .NET Standard and .NET platforms more clear; https://gist.github.com/davidfowl/8939f305567e1755412d6dc0b8...

Even if it had shipped, what's stopping them from skipping 5 and "turn it up to 6"? ;)

Not just in theory; http://www.mono-project.com/docs/about-mono/releases/4.0.0/

See https://github.com/dotnet/roslyn/issues/212

WPF is alive and kicking. I'll just leave this here... https://careers.microsoft.com/jobdetails.aspx?jid=137020&pp=...