• Commented on Perl and Me, Part 13: Here's To Future Days
    Outstanding series, really enjoyed it. Thanks!...
  • Commented on Showing Hidden Files on OS X and Time Machine
    For me, anything involving find, xargs and rm gets an echo in front of the rm first!...
  • Commented on JSON and alternatives and an extension proposal
    Douglas Crockford kept JSON simple for very good reasons that he discusses in a number of interviews. He left comments out on purpose after seeing them abused in HTML and other languages as ways of extending the language. He left...
  • Commented on Sexual Harassment?
    I think it is creating a hostile workplace. We techie guys underestimate this. Imagine that you are trying to get some serious coding done and yet every time you open a file, every time you page down, you need to...
  • Commented on A plan for revamping and replacing the Perl debugger.
    Why the need or urge to replace the existing debugger? A better one is great, but there are surely people who use the old one to great effect and know it like the back of their hands. Build a better...
  • Commented on When Perl is not applicable
    I feel uncomfortable posting a negative comment while knowing so little about the problem but saying "never do large data aggregation in SQL and Perl" is very provocative and forces me to comment, admittedly somewhat in ignorance. Your data set...
  • Commented on The Mind-killer
    I think the comments stand up fine without knowing anything about the app. Joel Spolsky's article was about the folks who want to throw away what they have and start over from scratch, and I completely agree with him. Refactoring...
  • Commented on A distributed design challenge
    Same caveat as yanick, except I didn't spend anywhere near 5 minutes on this! Is it feasible for everyone to know what percent of the budget is available? If so, slow down bidding on a campaign as budget limit is...
  • Commented on Do you remember when...
    Congratulations! I'm sorry I can't be there. Your organizing effort has been amazing, such a great job. Thanks!...
  • Commented on The Making of Mojocasts
    Beautiful job on the screencasts, looking forward to more! I've made a couple of screencasts, and the process you describe is exactly right. I didn't have iMovie and found the audio level to be a major problem. The whole process...
  • Commented on What's In A Name?
    How about But I like the renaming better....
Subscribe to feed Recent Actions from

  • Steven Haryanto commented on JSON and alternatives and an extension proposal

    Fair enough. Let me rephrase that: "The problem with using JSON".

  • Shantanu Bhadoria commented on JSON and alternatives and an extension proposal

    There is actually a dirty way to send images over json, Just base64 encode the image and put it in the json object like so :

    perl -MMIME::Base64 -MFile::Slurp -E'say encode_base64 read_file "test.png"'

    and then decode using
    perl -MMIME::Base64 -MFile::Slurp -E'write_file("test.png",decode_base64("BASE 64 FOR IMAGE HERE"));'

    little know fact is that you can even embed base64 encoded images directly into your img tags in html like so(doesnt work in IE)
    img src="data:image/gif;base64,FVaSDQJmEV8V4VpWIR8J5YZuIQvNrYJ+GTvFwXpu. . . "/

  • Steven Haryanto commented on JSON and alternatives and an extension proposal

    Yup, I'm aware of that. And by encoding to, say, BSON or YAML, you can also support e.g. array of icons (array of binary data) or other fancy data structures.

    But at this point we're already double-encoding. Why not skip JSON and directly encode using a format that supports the features we want?

  • commented on JSON and alternatives and an extension proposal

    The problem of double-encoding is not the number of encodings but a lack of rigor and clean encodings on each level. JSON is pretty clean and rigor, so it makes more sense to defined another encoding on top of it (examples: JSON-LD or RDF/JSON) instead of hacking on the encoding level of JSON. So please don't waste effort to extend JSON but make use of it to defined your own encoding.

  • Helmut Wollmersdorfer commented on Showing Hidden Files on OS X and Time Machine

    I always have ShowAllFiles on, because I need to see and edit

    .git .gitignore .htaccess .perlcriticrc .perltidyrc

    and others. Also I want to see the crap which OSX, Windows and (most) Linux desktop environments (DE) leave in directories. It's a shame for Apple that you need a script for switching this mode. Nearly every other DE let you switch this in the menue 'View'.

    BTW: Because of the courious treatment of filenames in OSX special care should be taken (keywords: Case Conservation, Escaping) .

Subscribe to feed Responses to Comments from

About is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.