Perl is for delivering things to the browser. Once on the browser, it's all about JavaScript. You would remain much saner if you separated your concerns between services provider and client. The client can be anything (a browser, library, etc) - but you're limited to JavaScript based solutions on the browser. I'd look heavily into REST and providing an API on the server side. As I said, if the REST API is decent, you can write a client in anything - so for example, you could bypass the browser altogether and write a nifty GUI client using Perl + some bindings for a Tk or some other GUI library.

In reply to Re: What's this I hear about Client Side Perl? by perlfan
in thread What's this I hear about Client Side Perl? by taint

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.