--- AnyEvent/lib/AnyEvent.pm	2008/04/07 19:23:59	1.41
+++ AnyEvent/lib/AnyEvent.pm	2008/04/07 19:42:18	1.44
@@ -20,7 +20,7 @@
    $w->wait; # enters "main loop" till $condvar gets ->broadcast
    $w->broadcast; # wake up current and all future wait's
 
-=head1 WHY YOU SHOULD USE THIS MODULE
+=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
 
 Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
 nowadays. So what is different about AnyEvent?
@@ -40,9 +40,8 @@
 module users into the same thing by forcing them to use the same event
 model you use.
 
-For modules like POE or IO::Async (the latter of which is actually
-named confusingly, as it does neither do I/O nor does it do anything
-asynchronously...), using them in your module is like joining a
+For modules like POE or IO::Async (which is actually doing all I/O
+I<synchronously>...), using them in your module is like joining a
 cult: After you joined, you are dependent on them and you cannot use
 anything else, as it is simply incompatible to everything that isn't
 itself.
@@ -61,6 +60,10 @@
 offering the functionality that is useful, in as thin as a wrapper as
 technically possible.
 
+Of course, if you want lots of policy (this is arguably somewhat useful
+in many cases) and you want to force your users to the one and only event
+model your module forces on them, you should I<not> use this module.
+
 
 =head1 DESCRIPTION