POE is (in my opinion) a bit grottier than some other solutions might have been, but certainly not on the "shrieking horror" level of Expect. ;) There are many different sugar layers built atop POE, but I'm now using MooseX::POE, which is nice. It's not a disgusting pile of hacks, unless you think that everything in Perl is that, in which case... y'know.
For example, IO::Async lets you do your work with futures, which are a very nice abstraction that people from many other languages are used to. You can do that in POE, but it's not the default way. POE also has, sometimes, weird choices of jargon for stuff. I know POE better, though, and my goal was to get it done, rather than learn a new framework or build something to last the ages. I mean, the kid might stop being interested in Minecraft at any second, right?
For example, IO::Async lets you do your work with futures, which are a very nice abstraction that people from many other languages are used to. You can do that in POE, but it's not the default way. POE also has, sometimes, weird choices of jargon for stuff. I know POE better, though, and my goal was to get it done, rather than learn a new framework or build something to last the ages. I mean, the kid might stop being interested in Minecraft at any second, right?
And yes, it was mjd.