If today you still run an application on Mono, I suggest you assert again whether that decision is sustainable. A look back on the Mono history can easily tell that it can be a risky platform to use in 2021 and beyond.

I wrote a language server prototype for reStructuredText in 2017 (let’s call it rst-antlr), which helped create some basic functionality in the reStructuredText VSCode extension. But in the next few years I didn’t have too much time to extend it further.

That approach has several limitations,

1. The language parser in C# is rather hard to improve, as the original language specification and implementation is Python based.
2. Too many gaps are there to fill.

It was a few weeks ago that I noticed MongoDB guys launched a language server for their internal documentation system named Snooty, and that language server contains reStructuredText support, which is based on docutils. And no doubt, time to integrate Snooty with reStructuredText VSCode extension.

Again this post comes from a Stack Overflow thread.

.NET 5 was released a few weeks ago, and 2020 is coming to an end. So now let’s talk about the stories around .NET Framework Reference Source, which almost always stays in the shadows.

Microsoft abandoned MonoDevelop GitHub repository earlier this year, and we can see no commit was pushed since February. However, there is no official announcement from any Microsoft channel on why that happened.

WinUI was developed as part of UWP and has been the foundation of many Windows 10 apps. Uno Platform implements the same API surface on non-Windows platforms, so some applications can be migrated to iOS/Android/macOS (and even the Web via WebAssembly). But how difficult can such a migration be? In this series of posts, I will try to cover the story to migrate Files UWP, a medium size open source file explorer, to macOS.