Most people will probably still just say "perl".
But what is the trademark status?
(As for Perl 6, we've already got "Rakudo Perl" and other Perl 6 dialects, so there's no need to have "Rakudo Blackfriar Perl" or something as Will appears to suggest.)
I'm glad that the name "Onion Perl" hasn't been suggested, since that might imply that there is Only One Perl. There isn't, and in the future, we might even have another sibling in the so far fairly small Perl family of languages.
]]>C<>
sequences). I like both… except the list thing, which bites.
(I wonder if there is any chance we can hope for POD to gain better list syntax… maybe via an approach like Dist::Zilla it could be introduced in such a way that old infrastructure continues to work. (That is what makes it hard to add significant features to POD.))
]]>I have one more thing to (add|ask). Is there a way to collapse (a la orgmode) POD sections in Emacs? That's the other (out of two) pet peeves of mine regarding POD.
]]>Have a look at Pandoc. It's got tasteful enhancements to original Markdown. Great for writing documentation.
]]>For simple bullet/numbered lists, Markdown is fine. But if each list item has multiple paragraphs interspersed with code samples, I'd say Pod is a more attractive prospect.
]]>https://github.com/jjn1056/Perl-Catalyst-AsyncExample
If you wanted to try Catalyst and give me some reports, you could help make it better for everyone!
John
]]>a) Someone calls a web service to my web app, which is backended by non-async stuff like DBIx::Class.
b) You add something like this to your code:
after insert => sub {
my $self = shift;
send_message_to_pusher($self->message);
};
c) Meanwhile applications around the world are subscribed to the pusher queue, and they all get the instant event update from pusher.
That's, of course, a gross oversimplification, but I hope it explains why and how Perl is involved.
]]>I'm the author of Firehose.io. The nice thing about Firehose is that its a plain' ol' HTML PUT request to a URL, which is the same URL that all of the clients are listening to.
Hit me up on Github or the Mailing list if you need help figuring it out, but it should be pretty simple (that's what I gun for).
Cheers!
]]>I've been thinking about launching a hosted version of Firehose.io for the very use case you mention. I know its too late to convince you to use Firehose.io (sunk costs!) but I'd love to know what provider and plan you ended up choosing if you don't mind me asking.
]]>