This is a good example[1] at 64k LOC removal. We removed built-in support for C# + WinRT interop on Windows and instead required users to use a source-generation tool (which is still the case today). This was a breaking change. We realized we had one chance to do this and took it.
I quite enjoyed both series. They are not similar (as you implicitly suggest).
Wayfarer bugged me at first because each book is a massive departure from the next (somewhat like Ender 1 and 2). As much as it pained me to leave the characters of the first book, the following books were more meaningful and stayed with me much longer.
This is all true. The only part that is potentially misleading is that the target doesn't need to be a blog. A blog is a fine target, however. The key activity is spending time to articulate a message with enough clarity that another person will understand what you meant and that they will conclude there is some value in it. There are lots of avenues for this.
It's not limited to this, but in the workplace I think of this as "write it down culture". People who write things down often have the most tested and credible ideas, with the first and most important judge being themselves.
The bulleted list in the design point section is intended as a high-level summary. We may do another post later that is part-way between the bulleted list and the post as a whole. Perhaps that would be the last post in the series.
Post author here -- There are lots of resources for teams within Microsoft. Please reach out and we can help you speed up that process. Contact info in my profile.
We work super closely with teams and often post about their fine work and even finer results on our blog.
We started with Red Hat. They were our .NET Core 1.0 launch partner (and remain a very close partner). You can run Red Hat on-prem or in the cloud (obviously).
We maintain container images for both Linux and Windows. I can tell you that they both get a LOT of use (>10M pulls/month). .NET is very much a cross-platform app stack. Also, we get plenty of bug reports on Linux (which we diligently fix). The days of .NET being Windows-only (and closed source) are long over.
Fedora and Red Hat have offered .NET packages for years. We've worked very closely with those folks and they've taught us a lot about how to work collaboratively with distro maintainers. We meet with them weekly. Notice that Fedora is mentioned in the blog post and here: https://docs.microsoft.com/dotnet/core/install/linux#officia....
I've read that one. It's good, but not nearly as good as her other writing. I'm always torn by whether I like the earthsea or Hainish series better. She also has many wondering short stories, some of which borrow from her longer works.
https://learn.microsoft.com/en-us/dotnet/csharp/language-ref...