Okay, so an IoT BBQ is a useful thing. How are we going to prevent every single useful thing from coming up with its own crappy, poorly-maintained application? Because obviously having open standards is not enough. So far the solution we've come up with seems to be "wait until one or a few companies dominate the market, come up with their own solution, and hope it's an open one and/or others adopt it." This particula…
Is that necessarily something we want to prevent? In the context of the early Web, should we have prevented any company from making their own website? Enforced some standard for how your website UX should work in the name of security and usability? Obviously not, as that diversity has led to more, better choices over time, and in the end the better UXs usually win out anyway. Perhaps in a similar way, as Weber and ot…
Well, websites are now a bundle of arbitrary remote code execution called javascript, we didn't allow that, so by today's standards, ya we did.
> Enforced some standard for how your website UX should work in the name of security and usability?
Well, html, so ya, again, ya we did. And we could again. A lot of the functionality of apps simply don't justify requiring you to run a program.