3 ms·

Line-oriented text-based interfaces strike again! I haven't used Perl in years, but I'd like to know why the POE approach is groty. I'd prefer writing the thin

Line-oriented text-based interfaces strike again! I haven't used Perl in years, but I'd like to know why the POE approach is groty. I'd prefer writing the thing in Perl than Expect. As a dad waiting eagerly for his son to be old enough to play Minecraft, I'd much rather run an unmodded server, so this approach is very appealing to me. I've been disappointed that almost every pre-release for 1.8 had nothing but server commands, but if it means I can drive a Minecraft server without mods I see more value to that effort. I'm curious if the Dominus mentioned in the article is mjd. I saw him speak once on how git was a greater accomplishment for Linus than Linux. At 37 years old, I'm trying to find a path forward in my career that lets me keep growing as a programmer. It's encouraging to see these hackers who have stayed with their craft all these years and are still churning out cool solutions.

rjbs 12y ago
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? And yes, it was mjd.