4 ms·
A good black box relies on the assumption that the inputs / outputs are well documented and true to their spec. This is a very unsafe assumption, at least unti
by lordlimecat 6y ago
A good black box relies on the assumption that the inputs / outputs are well documented and true to their spec.
This is a very unsafe assumption, at least until we invent a programming language that disallows bugs of any class.
- alisonkisk 6y agoWhat's the point of a philosophy that is impossible to live up to. Nobody audits a substantial fraction of their dependencies.
- bpt3 6y ago> What's the point of a philosophy that is impossible to live up to. Nobody audits a substantial fraction of their dependencies. It's a choice to be ignorant of your dependencies, not a law of nature. The fact that most people don't audit code they depend upon is a problem to be fixed, unless the underlying code is fixed first.
- a1369209993 6y ago> Nobody audits a substantial fraction of their dependencies. I do! In fact if we exclude the language implementation itself[0], a plurality of my projects have NaN% of their dependencies fully audited. 0: ie, compiler, hardware, etc; if you object to this, please do explain how to eliminate these dependencies; I'm quite interested.