Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

Alias
  (email not shown publicly)
http://ali.as/

Journal of Alias (5735)

Monday September 10, 2007
11:30 PM

JSON::Tiny?

[ #34413 ]

Someone that I've been talking to about YAML::Tiny in email asked my opinion on CPAN's JSON modules, and whether or not I had any plans to write a JSON::Tiny as well.

I replied at the time that I had no idea, since I had never really taken a good look at JSON-related modules before, and I only created ::Tiny modules where ALL the existing options were either bloated or XS-based, and there was a genuine need for a ::Tiny module.

And so far I think I've managed to hold the suffix to that standard reasonably well.

Having a look around the various JSON modules however, it does indeed seem like all the JSON modules are indeed bloated or XS.

Personally, I don't need JSON::Tiny (we'll probably go with JSON::XS for this project by the looks, since XS is fine and it's close to a user interface and so the raw speed is important).

But by the looks of things there may well be a suitable case to be made for a JSON::Tiny, assuming someone can come up with a suitable API (personally I'd clone the Config::Tiny one) and a suitably small implementation...

(Disclaimer: This is NOT going to be the Vertical Metre of Beer challenge) :)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Would you be the "Master" of the ::Tiny namespace? If I wanted to do a JSON::Tiny would I send it through you for "approval" or something?
    • Well, no, Adam isn't the master of ::Tiny. He's just...

      ... the one who coined the term.
      ... the one who's going to come after you if you rebrand & upload SOAP::Lite as SOAP::Tiny. :)
      ... one of the PAUSE admins who process modules list registrations and give advice on choice of namespace.

    • "Guardian" perhaps?

      Or maybe "Brand Manager" :)

      As a suffix that I intended to be optimised for human factors (ease of installation, simple to use, and so on) I consider it an integral part of this that someone can see some ::Tiny module and trust that it does what it says, and that it's not just another ::Lite.

      That's in addition to the CPAN admin's natural dislike for naming bloat. If the ::Tiny suffix means something SPECIFIC, then it creates certainty and clarity around the meaning of it.