[ethbr0]

Snap's philosophy appears to be: Given the option to not patch, users will not patch. And this is even worse in IoT land.

Which I can't say is wrong.

Who probably shouldn't use Snap are users with mature patch application skills, who are willing the invest the time to review and patch regularly.

That class of users is far smaller than {all users}.

[indymike]

> Snap's philosophy appears to be: Given the option to not patch, users will not patch. And this is even worse in IoT land.

This is true. But there are so many situations where unpatched is better than bricked or bugged. The community's ask was reasonable.

[ethbr0]

Absolutely, the community's ask was reasonable.

But I think the goals might also be mutually exclusive.

Snap's philosophy, from what I read in the thread, boils down to: if an update bricks devices when it's pushed, the proper time to catch that update is before it's pushed, or as it's pushed, not after.

Which I do see the wisdom in. The majority of users are less well informed and equiped to test and patch than developers.