My experience with Midori people was a little like the jokes people tell about BMW owners and vegans.
You knew who they were because they wouldn't stop talking about Midori. It's a neat project, I liked hearing the stories.
Blogging about Midori (2015)
11–20 of 29 posts
Re: Blogging about Midori (2015)
#12Re: Blogging about Midori (2015)
#13> My biggest regret is that we didn’t OSS it from the start, where the meritocracy of the Internet could judge its pieces appropriately. This would have been interesting, but it's not too late. Correct me if I'm wrong, but there isn't anything stopping Microsoft from releasing this research to the public today. It seems like something the "new" Microsoft of 2020 would be likely to do.
There was a copy of the code for Singularity, the predecessor to Midori, on CodePlex. Not sure if it ever got moved to Github. It has to be said, though. It's more like "source available", not open source. I can't remember what the license is specifically, but it's not a proper open source license. You could see it, build it, and play with it, but you couldn't do anything else with it. No sharing changes, no derivati…
You can judge it, though.
Re: Blogging about Midori (2015)
#14See also "Safe Systems Software and the Future of Computing" by Joe Duffy, the closing keynote at RustConf 2017: https://www.youtube.com/watch?v=CuD7SCqHB7k Midori and Rust have several striking similarities, and Microsoft's recent uptick in interest in Rust (and Rust-like languages) bodes well for improved software quality.
The language team of that time participated also in the C# 7.2/7.3 performance wave and the technology which makes .NET Core so we'll performing nowadays.
Rust moves system programming up. At the same time, C# moves application development down. Interesting.
Re: Blogging about Midori (2015)
#15Everyone I have worked with from the Midori team has been very impressive. Regardless of the direct success of the project, I believe it (to some extent) improved the quality of Microsoft's engineering culture.
Engineering culture especially in he Windows NT kernel was always impressive. A search for David Cutler the lead behind Windows NT immediately also talks about engineering.
That said, Midori influenced later many team, including the .NET one.
Re: Blogging about Midori (2015)
#16Earlier quoted context omitted.
There was a copy of the code for Singularity, the predecessor to Midori, on CodePlex. Not sure if it ever got moved to Github. It has to be said, though. It's more like "source available", not open source. I can't remember what the license is specifically, but it's not a proper open source license. You could see it, build it, and play with it, but you couldn't do anything else with it. No sharing changes, no derivati…
You can judge it, though.
It was a really cool project. The software isolated processes concept is something that I really like.
Re: Blogging about Midori (2015)
#17Why was it called midori? My only knowledge of this word is that it means green is Japanese.
We brainstormed a bunch of names one day, and Midori won. I think it was Chris Brumme's suggestion.
Re: Blogging about Midori (2015)
#18My experience with Midori people was a little like the jokes people tell about BMW owners and vegans. You knew who they were because they wouldn't stop talking about Midori. It's a neat project, I liked hearing the stories.
I was on the Midori team for just a year, and this is certainly true for me. I think that it's a combination of things, the project itself was very cool from a pure technical perspective, and the team was made up of brilliant engineers, most of whom appeared to have nothing to prove, so technical discussions revolved about technical merit not ego.
Re: Blogging about Midori (2015)
#19My experience with Midori people was a little like the jokes people tell about BMW owners and vegans. You knew who they were because they wouldn't stop talking about Midori. It's a neat project, I liked hearing the stories.
I was on the Midori team for just a year, and this is certainly true for me. I think that it's a combination of things, the project itself was very cool from a pure technical perspective, and the team was made up of brilliant engineers, most of whom appeared to have nothing to prove, so technical discussions revolved about technical merit not ego.
There was a fair bit of ego.
Turns out when you have a project staffed with extremely high up engineers and no real production deployment, it's easy to keep up engineering standards. The idea that a normal team with normal issues wasn't as good seemed to really upset one of the midori people I worked with.
Re: Blogging about Midori (2015)
#20One comment at the time: https://news.ycombinator.com/item?id=10545353
Related from 2016: https://news.ycombinator.com/item?id=11054912
https://news.ycombinator.com/item?id=10871222