It's not slow. Because it uses inheritance, it's just as fast as not using it (other than the one time per process setup cost).

The reason I avoid it is because it defaults to JSON::PP. Your program could be orders of magnitude slower than required without any feedback that this is the case, just because you forgot to install the faster back end.

And also because it uses JSON::XS instead of Cpanel::JSON::XS. The author of JSON::XS is very contrary, and insists on keeping JSON::XS thread-unsafe, yet most Perl builds are threaded builds. I don't need this drama associated with that author.

(JSON will work with Cpanel::JSON::XS, but you have to explicitly tell it to.)

In reply to Re^2: Issues using boolean_values in JSON v4.02 by ikegami
in thread Issues using boolean_values in JSON v4.02 by bc3-au

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.