On Mon, Apr 11, 2011 at 5:07 AM, Meikel Brandmeyer <m...@kotka.de> wrote: >> What is your basis for this? > > Because the phantasy of the average human being is quite limited.
? > While a missed "this is allowed" might cause trouble, it doesn't > compromise the system. A missed "this is not allowed" however will. > Solutions are not always equivalent when you also consider system > robustness or fail safe or whatever it is called by the experts. That depends on the system. Some stuff is mission critical or really really dangerous. Then it makes sense to default to forbid. On the other hand, for a lot of other things, where security isn't a concern but utility is (e.g. single-user products), it may make sense to default to allow. > Just for illustration: Who designs a system, which starts an atomic > war on a bitflip in a test message? (Yeah, this happened and we are > only alive because of the gut feeling of an operator. Petrov? > The bombers were already in the air.) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
