Thoughts on update UX: maybe options should be "update now", "update later", "I don't use that functionality, remove it now".
Users should be taught "uninstall any background cruft you don't need to reduce attack surface". Doesn't work with spaghetti service crap.
-
-
No need for spaghetti deps - systems aren't designed so all their components are self-contained.
-
This is what we teach people to create: abstract the common stuff of A and B into C. You don't use B, great. Want to nuke C? Sorry, nope.
-
Will the customer ever understand what C is needed for? Why do they need to, in the first place? Is that a good use of their time?
-
No. Rather it's a good use of the system designer's time to ensure they don't have to do that in order to keep themselves safe.
-
I completely agree
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.