rickroller.myopenid.com

• Website: rickroller.myopenid.com/

Recent Actions

• Commented on Watching directories for new files
  I like the idea of File::ChangeNotify, but unfortunately, it unnecessarily uses Moose instead of something lighter weight like Moo....
• Commented on Updates to CPAN module reviews
  Suggestion- make a cpan-curation project on github to encourage others to contribute. That would be a great place to put your queue, as well as collect ideas for adding to the queue....
• Commented on Winobot, the IRC Bot You Can Party With
  What about KiokuDB?...
• Commented on Winobot, the IRC Bot You Can Party With
  I was excited with the AnyEvent mention, because I thought it would be efficient, fast and mostly portable. Then I looked at the requirements and my hopes were dashed- Perl 5.14 and MongoDB, not to mention Moose....
• Commented on DateTime is annoying
  why not submit a patch?...
• Commented on Learning AnyEvent
  I prefer AnyEvent over POE, but should point out there isn't really an AnyEvent community. There's Marc Lehmann (schmorp AKA schmuck) who develops it and the users. POE might suck when it comes to the API, memory use, speed, etc.,...
• Commented on Why does your site not link to perl.org?!
  There's some bigger companies listed on Wikipedia: https://en.wikipedia.org/wiki/Perl#Applications...
• Commented on Indonesian names for software projects/products
  I hope that doesn't mean you're going to stop naming your modules sensibly and take the ruby approach, where you can't figure out from the name what the thing does....
• Commented on Submit a Talk for YAPC::NA 2012!
  Let's hope the videos and slides of this years talks make it online, unlike those from last year....
• Commented on Writing API clients in Perl and Python
  WebService::Gett is probably a better name for your module. As Nick pointed out, Net should be avoided, and everything on CPAN is already an API, so that part is redundant....
• Commented on How should a JSON parser handle character strings?
  You're confusing character strings with byte strings. This is thoroughly documented in the JSON module. When dealing with character strings, use JSON::from_json or JSON->new->decode. Works fine....
• Commented on How to parse HTML, part 2
  Lot of theory, how about some benchmarks. Just noticed Marp::HTML requires perl 5.10, so I'm sticking with HTML::Parser because I have stuff that still needs to run on 5.8.9....
• Commented on Which Marpa distribution to use?
  why not do something similar to JSON? using Marpa would use Marpa::XS if available, and fall back to Marpa::PP otherwise....
• Commented on Announcing acme.cpanauthors.org and cpants.charsbar.org
  didn't take long for the new server to die also :(...
• Commented on Extracting your archives
  it would probably make sense to have Archive::Extract call Archive::Extract::Libarchive under the hood if it's already installed since Archive::Extract is used in so many places....
• Commented on Syntax highlight your SQL HEREDOCs in VIM
  Ovid, you've got so many juicy bits of vim, but I would really like to see how they all fit together. Any chance of adding your config to your github account?...
• Commented on CPAN modules for generating passwords
  I usually just shell out to `pwgen -1`....
• Commented on More Ouch
  Your version of try seems inadequate when compared to that of Try::Tiny....

Comment Threads

• mad.casual commented on Why does your site not link to perl.org?!

  I'm sure you know more than twelve sites that rely on Perl, perl.org isn't on there, cpan.org isn't on there... My point wasn't that 12 in the top 250,000 was THE %age of sites that use Perl. Rather that, your rebuttal seemed to split hairs between the idea that Perl's relevance is waning and that it's relevance is being pushed to the damp, musty, primordial parts of the internet that people don't visit. I wasn't trying to say you're wrong so much as you could be more convincing about the "hidden use and/or proliferation of Perl". Personally, I was searching for a pick-me-up that showed…

• hochgurgler commented on How should a JSON parser handle character strings?

  OK. It seems that the every other experienced Perl developer in the world is happy with the way the JSON module is prepared to deserialise from, and serialise to, character strings as well as byte strings. Only Pete Sergeant has a problem. Now, either Pete is a tin-foil-hat genius, and all the other experienced Perl developers are a bit thick, or Pete's missed something. Since Perl folk are a kindly lot, if Pete has a misunderstanding, we will try to help him.

  Let's say you hav…

• hochgurgler commented on How should a JSON parser handle character strings?

  Point of terminology: When I say "serialisation", I mean that a data structure is converted into a flat one-dimentional array of somethings, in this case (Unicode) characters. "deserialisation" is the converse.

  I think it is Pete who is at an impasse; the rest of the experienced Perl developer world is happy. The rest of the experienced Perl developer world could ignore Pete and happily go on about its business. The only problem with the status quo is where Pete is put in charge of a project and his failure to grok the…

• hochgurgler commented on How should a JSON parser handle character strings?

  In answer to your original question:

  My answer would be:

  If you pass the character string to an interface which provides byte-decoding sugar on top of the deserialisation, then it should, as you say, result in an exception.

  If you pass the character string to the interface which provides just the deserialisation, then it should deserialise the character string into the relevant Perl data structure.

  Taking your example string

  ["Eat More Turkey ★"]

  T…

• schmorp commented on How should a JSON parser handle character strings?

  I may be a bit late, but I am mostly with Pete here...

  JSON parsers often accept JSON texts in various encodings - utf-8 is obviously very common. They sometimes also accept unencoded JSON, which, IMHO, isn't valid JSON text (a perl string isn't "encoded in unicode", it *is* unicode, which isn't encoded in any way).

  So apart from changing "ASCII" to "characters with codes >255", Pete is right: if a JSON parser is asked to decode UTF-8 encoded JSON text, then it should (at least optionally) signal an error on invalid input. \x{2222} is invalid in utf-8 encoded json text (as w…