3 ms·
Hmm, if it's on the local box and not actually going over a network, like the poster implied, I don't think it would be so bad; assuming it's just a call to do
by mquander 17y ago
Hmm, if it's on the local box and not actually going over a network, like the poster implied, I don't think it would be so bad; assuming it's just a call to do some oddball library thing here and there, and not in the computationally intensive portions.
- lukev 17y agoStill. You're likely to incur at least a few milliseconds of latency on the HTTP call, and most "eval" implementations I've worked with are prohibitively slow. I haven't benchmarked other languages, but I was using it in a Groovy app until I realized each call to eval was taking over 100ms. Even granting that Groovy is a dog, parsing from a string is non-trivial. At that point I'd ask myself whether it was worth the trouble.