> Beginning in macOS 10.15, notarization is required by default for all software.
Taken from https://developer.apple.com/documentation/security/notarizin...
Web, iOS, watchOS, iPadOS, Android, ChromeOS all use some form of sandboxing.
So unless your alternatives are the 1% GNU/Linux desktop market, sandboxes are here to stay.
ChromeOS supports android apps, but yes, I would state that iOS, chromeOS and android are really bad operating systems.
"Linux for Chromebooks: Secure Development"
> Learn how Linux for Chromebooks (Crostini) gives you a secure sandbox for development. Through a variety of demos, this talk will explain the architecture underlying Linux for Chromebooks and the design decisions that keep it easy to use.
https://www.youtube.com/watch?v=pRlh8LX4kQI
And Android:
"Adopting the Arm Memory Tagging Extension in Android"
https://security.googleblog.com/2019/08/adopting-arm-memory-...
"https://developer.android.com/distribute/best-practices/deve...
https://developer.android.com/distribute/best-practices/deve...
"Improving Stability with Private C/C++ Symbol Restrictions in Android N"
https://android-developers.googleblog.com/2016/06/improving-...
"Android NDK Native APIs"
I am not interested in side loading anything. I have just no interest to use an API that is abused to promote a proprietary store and an OS because I only see disadvantages in that. UWP may have changed by now, but for me it is too late. I have switched to other technologies and are pretty happy with them. If windows continues to be SaaS, I will not develop for it. Even if its legacy might continue for a few decades.
If the primary form of deployment is a store, I could as well use Apple. Although their store isn't really shining on Mac OS as well. I believe there are good reasons for that.
Windows as a platform had many advantages, but it seems to me that MS threw that away to emulate others. A futile strategy in my opinion.