in reply to Re^3: What's this I hear about Client Side Perl?
in thread What's this I hear about Client Side Perl?

Thank you, tobyink, for such a long, and informational response -- you must be in Book Writer mode. ;)

Honestly, my aversion to JavaScript isn't that I dis-like it, so much as that it seems a bit fragile (easily disabled), and, if at all possible, I like to keep things in the same language. It's more efficient, and tidier. Less maintenance, and housekeeping too.

Something else that that frustrates me, is that Perl, and JavaScript are so darned similar. Yet, Perl isn't scriptable at all on the Client-Side. But then again, then it'd just be JavaScript, and I'd still be complaining. :P

Anyway, it seemed that maybe serialization might hold some sort of solution. While I've had little time, working with it. Is seemed it might hold some possibilities. Albeit probably a little less responsive.

All of this is why I've posed the question(s) here. With all the vast accumulated knowledge the PM holds collectively. I was sure that if anything in this area was possible. Surely a Monk would know. :)

Thank you again, tobyink for all the information.

--Chris

ˇλɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

  • Comment on Re^4: What's this I hear about Client Side Perl?

Replies are listed 'Best First'.
Re^5: What's this I hear about Client Side Perl?
by Your Mother (Archbishop) on Jun 04, 2014 at 06:39 UTC
    I like to keep things in the same language

    You can do server side in JS just fine… e.g. node.js.