|laziness, impatience, and hubris|
I'm the one pointing out that you're making a wild assertion (paraphrasing, "BLOCK eval causes an order of magnitude(s) slowdown") which runs counter to consensus experience without giving any concrete evidence or providing any sample code which evidences the problem in question by myself providing a counter example, yes.
Show us code which evidences this purported order of magnitude(s) slowdown and I bet you'll get a reply from someone either pointing out what you're doing wrong, or if it's actually something you'll have eyes look at it from someone quite likely to be able to fix the problem in perl itself. BLOCK eval does add a small overhead because of the extra steps involved, but not that much (it's a couple of extra opcodes in the tree that don't really do much of anything if no exception occurs).
Or keep whinging about downvotes because you posted something detail- and code-free that (observationally) most people reading think is bunk. Tomayto, tomahto.
Edit: Tested the same benchmarks with a 700+k character "NON-TRIVIAL" chunk of both valid and invalid JSON (the later made by substituting in random garbage somewhere in the former). Aside from the processing rate understandably going down with the larger amount to parse the results look similar showing that the presence or absence of eval has no measurable effect (hundreds/sec for the non-PP versions versus 30k/sec; PP gets on the order of 1/sec eval or no).
The cake is a lie.
In reply to Re^3: Can someone please write a *working* JSON module