John Gabriele

• Website: www.unexpected-vortices.com/
• About: todo: write an "About" blurb.

Recent Actions

• Commented on Pod to HTML
  I’d be surprised to see this done in Markdown without drastic extensions to the point where it is no longer Markdown. Have a look at Pandoc. It's got tasteful enhancements to original Markdown. Great for writing documentation....
• Commented on Pumpkin Perl Breakdown
  I think one item is missing in the "Why" section which should be explicitly included: "If you currently use Perl 5, but also think that Perl 6 is Perl's future: ..."...
• Commented on Pumpkin Perl - Redux
  Thanks for the reply, Matt. Can you please tell me, would Pumpkin Perl manifest itself as something like `/usr/bin/pumpkin`, whereas Perl 5 would stay `/usr/bin/perl`? I do really like the name Pumpkin Perl, btw. Creative, connects with Perl history, and...
• Commented on Pumpkin Perl - Redux
  Ooh, some other fun little benefits of using "Perli" which come to mind: "Pearly" sounds nice. (silly) "Here is the Perlian way to do that ..." :) The name change should be technically non-disruptive, since it's still a one-word name...
• Commented on Pumpkin Perl - Redux
  Here's one more idea to consider: Name the next version "Perli". It would be Perli 1.0.0. You can pronounce it "Perl eye", "Pearly", or "Perl improved" if you like. Benefits: the name indicates obvious connection with Perl the name only...
• Commented on Names and Numbers, Brand and Identity
  So, there would then be 3 Perls: * Perl 5.x : stays backward compatible with Perl 5 * Pumpkin Perl * Perl 6 Is that correct? If so, would Pumpkin Perl start seeing backward-incompatible changes which won't make it into...
• Commented on My Prediction
  If you want to change the version numbering to show users the vintage of the release, but also not snub Perl 6, maybe version it like so: Keep the 5. Also include the year. Like so: Perl 5.2013. Any further...

Comment Threads

• raiph commented on Pumpkin Perl Breakdown

  I liked everything about mst's original Pumpkin post with one small exception -- the specific qualifier Pumpkin.

  In most ways it's outstandingly good. But it didn't leave me 100% satisfied.

  I've just seen someone's suggestion of Modern Perl, and I have to say I like it a lot. I checked whois, and shadowcat owns modernperl.com...

• Christopher Cashell commented on Pumpkin Perl Breakdown

  I like it.

  The name "Pumpkin" isn't necessarily my favorite, but I'm pretty sure that's just pure personal opinion; I can't think of any real objections to it, nor can I think of a better suggestion. There's certainly nothing wrong with it.

  I do still like the idea of year-based versioning, ideally along with the name change. If you're going to do releases based on a scheduled time-table, it makes sense to match your versions to it. However, that's something that can be considered in the future.

  I'm feeling good about this change.

• Neil Ostrove commented on Pumpkin Perl - Redux

  It looks like most of the comments like the idea but dislike the name, mostly because its meaning isn't obvious. To give everyone a worse choice to rally against, thereby consolidating mst's choice, I hereby propose the name Acoustic Perl (analogous to acoustic guitar).

• Toby Inkster commented on Pod to HTML

  I dunno.

  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.

• Mohawk commented on Pumpkin Perl Breakdown

  From http://irclog.perlgeek.de/perl6/2014-09-05#i_9305941 (freenode/#perl6) a few minutes ago (edited to correct spellings):

  20:16 	mohawk 		TimToady: if perl5 were to be re-branded as Camel Perl (subject of course to a conversation with Mr O'Reilly), how would you feel about that?
  20:16 	* TimToady 	thinks it wouldn't make any substantive difference
  20:17 	mohawk 		are you "no strong feelings one way or the other"?
  20:17 	* TimToady 	thinks people …