Blogging about Midori (2015)
joeduffyblog.com
Blogging about Midori (2015)
1–10 of 29 posts
Re: Blogging about Midori (2015)
#2Re: Blogging about Midori (2015)
#3This 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.
Re: Blogging about Midori (2015)
#4Why was it called midori? My only knowledge of this word is that it means green is Japanese.
Re: Blogging about Midori (2015)
#5https://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.
Re: Blogging about Midori (2015)
#6Re: Blogging about Midori (2015)
#7Re: Blogging about Midori (2015)
#8Earlier quoted context omitted.
Wild guess: it's a Greenfield OS project
I had never heard of this, but thank you.
Re: Blogging about Midori (2015)
#9Why was it called midori? My only knowledge of this word is that it means green is Japanese.
Re: Blogging about Midori (2015)
#10> 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.
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 derivatives, etc.
Singularity would be a neat place to start working on a managed code OS, though.
I would prefer that they properly open source Midori.