2 ms·
Hmm. This is an interesting topic to think about. Why aren't the tools for analyzing White Boxes as good as those we have for Black Boxes? I would say it's due
by falcolas 12y ago
Hmm. This is an interesting topic to think about.
Why aren't the tools for analyzing White Boxes as good as those we have for Black Boxes? I would say it's due to the differences in boundaries.
For example, Black Box tools have it simple. Capture anything that crosses in the direction of Black to White. Capturing what goes from White to Black is much harder, though, since there are less visible boundaries on what can be accessed. For example - if I write a black box which utilizes a environment variable, you have to be tracking what memory a program accesses to see this from outside the program.
White boxes, on the other hand, have very few boundaries, and those which exist are fuzzy at best. Sure, there are technically functions and modules and scopes, but these boundaries are soft; frequently and easily pierced. Global variables, shared memory, inlined functions, tail call optimization, continuation passing... all of these make it incredibly difficult to reason about and trace program flow, because the program flow depends so heavily on the global context.
Functionally pure programming paradigms might be our best bet in the long run: when a "function" produces deterministic output for given input, we suddenly create a network of predictable black boxes within our white box, giving us the edges we need in order to implement our tracing and automated reasoning tools.