WSL2: Code faster on the Windows Subsystem for Linux!

Tanaka Jimha tells us all about MSIX, the package format for installing Windows apps, including how to package your existing code with Visual Studio and how to deploy and distribute your app, via the web, the Microsoft Store, or an Enterprise distribution network.
A file with the .msix extension is a Windows application installer and an updated alternative to .exe, .msi, and .appx packages. MSIX preserves the functionality of your existing app packages and/or install files, in addition to enabling new, modern UI features and deployment options for Win32, WPF, and Windows Forms apps.
Here are some links to learn more:
Certificates and signing still cause too much friction for me to use this. I tried to create an .msix package for https://github.com/mike-ward/tweetz and was immediately confronted with generating a cert and installing it. That's a fail for me right there. I'm also confronted with how I get the certificate to GitHub and use it in Actions. I need an "Easy Button" and this ain't it.
Maybe GitHub Actions could provide a certificate at build time? One associated with my account perhaps?
I do not hear about why msix is better and why move towards it.
He only say "you modernize..." and "as mentioned "unaudible blabla" at 1':09"...
Where is that mentioned please?
He is probably referring to the MSIX documentation, the link is provided above. Check out key features and highlights.
but not even microsoft edge uses msix, let alone any of their partners (like spotify, google, adobe, etc). if microsoft can't commit to it, why should anyone else?