Thanks, sorry for my tone yesterday. It was the end of a long frustrating work day.
Azure Linux does look interesting, thank you for working on it. Fedora is a great choice as a base image. Having a Fedora based distro designed to work well with WSL would be amazing! As a base image for apps though I'm curious how you manage the 6month release cycle. Are you planning on expended support, or would people using it need to upgrade every 6 months. I think the appeal of a Debian base is we only need to think about big upgrades every 2 years.
A few bits of Azure feedback I can think of now. Probably not directly related to what you work on, but just some of my experiences working with Azure for the last year.
1. The CLI is good, I think maintaining feature parity between the CLI and portal is really helpful and allows us to integrate with our internal infra more easily. Azure CLI is really the best part working with the service.
2. The management portal is really flaky. Like unknown error messages pop up when clicking on deployment logs. Sometimes the SSH or log tail functions just don't load at all and overall the experience just feels sluggish. I'm really not sure what can be done about this but I've been moving to the CLI just because the web interface is frustrating to work with.
3. The Microsoft documentation is really verbose and difficult to navigate in my opinion. Like we were looking in to hosting a Teams bot and those docs are full of emoji and full page articles like 'why did we make an SDK?'. I have to jump around several pages to get to what I need and even then the code examples in the docs are not actually in sync with the current version of the SDK library. It feels like AI was just set loose to write as much as possible. I think the problem is the information density of much of the documentation is very low. Maybe that's something that can be addressed going forward.