And furthermore, you could quantify the severity of the expected holes per "access tier". So if you have n layers of JavaScript crap, and m layers of browser/platform code, expect O(!(nm)) JS-level exploits and O(!m) platform exploits. Etc., etc.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
And you know someone will say "It blows up exponentially!" when they see that.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
How do you design a robust mechanical device? Minimize the number of moving parts. How many "moving parts" does a thing like office365 have?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Point of order: Layered frameworks/libraries, which is the overwhelmingly common case, are not stacked in arbitrary order. If A requires B, then B does not typically require A. So it would be O(2^n) not O(n!).
-
I would say, with the exception of specific tier split points, often times A and B interact bidirectionally to produce holes. Like all JavaScript interacts bidirectionally, for sure.
- Show replies
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.