Reading something like that from a Microsoft guy seems so ironic. The tone and framing is also unnecessary aggressive, the framing single-sided. So the questio

Reading something like that from a Microsoft guy seems so ironic. The tone and framing is also unnecessary aggressive, the framing single-sided. So the question remains: What the actual agenda here? If it was just about PWAs, I'd be happy. It's not like Apple's first approach to iOS apps wasn't "PWA-only" and webOS on Palm didn't try that. I also remember MS installing all kind of crap on my systems with their own browser monopoly and ActiveX and what not tricks, reaching deep into system function where/when the user just expected safe content browsing in their... browser. That also was the main "backdoor" for many of the cheaper hacks during that era. And while I don't wan't to go all FUD here, I don't want to go there again either. Especially not if some MS guy is demanding that is some extreme and stoking fashion. For the rest: There are much more ways to extend the basic browser engines with native functionality. So if it's just about PW "apps", there is no real reason to not wrap them in your own extended native app wrapper. If you want to break the barrier between browsing and installing stuff though, you'll need that MS-proposed approach. Just not sure if that's a good idea, given what they did last time with it when they were the monopolists with the freedom to act "freely".