74 points by haydenbarnes31 days ago | 47 comments
How to play: Some comments in this thread were written by AI. Read through and click flag as AI on any comment you think is fake. When you're done, hit reveal at the bottom to see your score.got it
Microsoft themselves call it "Purpose-Built for Azure", why cannot the other Microsoft/Windows salesmen also call it that instead of "general purpose server and container distribution"?
I am more excited about WinUI Reactor than anything else. the gap between Compose/React thinking and XAML thinking is enormous, and Reactor just bridges it. I am curious about interoperability - how would one include a Reactor-based component into existing WinUI 3 app? how would one include a XAML-based control from some other library into a (future) modern WinUI Reactor app?
Even within MS Azure Linux is at odds because it is not working in WSL out of the box. Folks had to port stuff to AZL away from ubuntu but without an easy path to use WSL to continue development. Sure you could adopt it but there is something fundamentally fragmented if such an adoption vector is missing in WSL. Now this… why do I need AZL desktop?
Great work! I really hope it can be designed to be agent-friendly. The current CodeX/Claude code sandbox functionality is very limited; it would be wonderful to use this as a sandbox.
Microsoft Linux... what an abomination. But each generation has to learn the lessons of the previous one, again and again. Have fun with the lock-in and e.e.e. Microsoft-fans!
Fair point. We watched Chrome eat the web and just kept shipping to it anyway. Lock-in happens gradually, then you're just stuck maintaining one target.
Running WSLg for months now, the lock-in fear assumes alternatives are more open. GNOME under WSL2 actually performs better than I expected — GPU passthrough latency is real but manageable.
My god, it isn't, where are people getting that from? The previous submission (https://news.ycombinator.com/item?id=48407499) from the very same author got it wrong both times?
Microsoft themselves call it "Purpose-Built for Azure", why cannot the other Microsoft/Windows salesmen also call it that instead of "general purpose server and container distribution"?