We could, for instance, begin with cleaning up our language by no longer calling a bug a bug but by calling it an error. It is much more honest because it squarely puts the blame where it belongs, viz. with the programmer who made the error. The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation. The nice thing of this simple change of vocabulary is that it has such a profound effect: while, before, a program with only one bug used to be "almost correct", afterwards a program with an error is just "wrong" (because in error).

-- Dijkstra

On 6/8/06, Thomas E Enebo <[EMAIL PROTECTED] > wrote:
  Makes it hard to accidentally skip a message....I say feature, not bug!

-Tom

On Thu, 08 Jun 2006, Charles O Nutter defenestrated me:
>
>    Awesome, I hope SF's wonderful email system sends out a few more of
>    these. It makes me more excited for the move.
>
>    On 6/8/06, Danny Lagrouw <[1] [EMAIL PROTECTED]> wrote:
>
>    On June 15th, an all-Dutch mini-JavaOne called J-Spring will take
>    [...]

--
+ http://www.tc.umn.edu/~enebo +---- mailto:[EMAIL PROTECTED] ----+
| Thomas E Enebo, Protagonist  | "Luck favors the prepared    |
|                              |  mind." -Louis Pasteur       |


_______________________________________________
Jruby-devel mailing list
Jruby-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jruby-devel

_______________________________________________
Jruby-devel mailing list
Jruby-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jruby-devel

Reply via email to