Would be interested to hear more, but from the outside it appears they spent 10 years doing stuff but never really had a path to shipping something commercial nor integrating/improving Windows.
> From what I've read (https://joeduffyblog.com/2015/11/03/blogging-about-midori/), Midori was a research project, and not a replacement. They started with .NET and C# because they own it, but then departed to custom languages. Their research included stuff like language safety (most of it now in Rust, and it seems they implemented some of it into C++ and C#). Also cool concepts like capabilities instead of permissions (2. post), programs that are multiple separate processes (like Smalltalk's; the lessons learned are now in C#'s await keyword), etc. The articles are a nice read.
Most of the stuff in Midori never made it out of the project at all, partly because a lot of the ideas weren't that great tbh.
This https://www.youtube.com/watch?v=37WgsoZpf3k and a bunch of follow-up videos on the channel shed the light on the technical side of things. As someone working on a somewhat performance-sensitive project, just one of the features - safe immutable and slice-eable buffers from the OS to enable fully zero-copy buffer handling already sounds like an excellent tool to have.