Future of AnyEvent?

Art Sackett asackett at gmx.com
Thu Jun 22 07:14:17 CEST 2017


Greetings:

My apologies if this has already been addressed; I try to read
everything that flies through the list but sometimes life gets busy and
I skip a few days. Has there been, or is there any hope of, progress in
keeping AnyEvent from being driven to extinction by p5p?

This:

	https://rt.perl.org/Public/Bug/Display.html?id=119433#txn-1292226

... summarizes the issue nicely, I think, even if the issue then at hand
has been resolved. What got me thinking about it again is that I just
upgraded Debian to v9.0, which brought me perl 5.24.1, and AnyEvent
install via CPAN gives me a failure of t/12_io_ioaio.t "not loadable".

Not that it matters, but having just been forced to address this problem
in my own world has got me thinking that perl has managed to reduce
itself to a toy language. As just one easy example:

	$ perl -e 'say("hello")'
	Undefined subroutine &main::say called at -e line 1.

	$ perl -e 'use 5.10.0; say("hello")'
	hello

We got a new pragma to turn on the new features. BUT when they yanked
'.' from @INC it was without that consideration; we don't get 'use
voodoo::security'. Instead we're told by some in the community (whose
opinions have prevailed) to blame ourselves if we get upbreakage, and by
others in the broader community to blame ourselves if failure to update
allows our systems to be cracked. If both of these assertions of who's
to blame are true, then one who wishes to avoid that blame has but one
rational choice: *stop using perl*.

Which is why I'm asking about AnyEvent's chances of avoiding extinction.
I can live without perl a lot easier than I can live without libev and
libeio.

Thanks in advance for any useful words! 

-- 
Art Sackett
http://www.artsackett.com/



More information about the anyevent mailing list