Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Since about 1996 some were convinced that a Web Browser could serve as the ideal 'cross platform solution' for generating language-agnostic GUI front-ends. Ironically, it was about that time that several companies sprang up, offering 'virtual desktop' software that you could run over the internet, complete with DHTML-based widgets that looked just as good as (and in some cases even better) than the GUI components your typical Windows (TM) user has come to expect. (you might be very surprised by what can be rendered in a typical browser, see eg http://www.bindows.net/ )

The dotBomb explosion and browser incompatibility hassles helped to wipe most of these ventures off the map, but the fundamental idea is still feasible, and still remains critically overlooked by *most* developers:

The 'web' browser sitting on most computers is perhaps the most flexible and most amazingly underused component for GUI-based development.

The single most enduring circumstance that prevents serious progress in this area is the lack of a language-neutral and credible mechanism for interprocess communication between the browser GUI front-end and perl. (or whatever your language of choice is).

OOP enthusiasts will parrot the virtues of "loose coupling" until they are blue in the face, but the sad fact is, we are still in the archaic "stone age" when it comes to options for GUI development. We shall not emerge from this primitive state until it is possible for a GUI developer to create a front-end with absolutely *no need to know what 'language' will be used for the 'back end'*. The technology exists to make this possible today, but not enough people 'get it'. That is especially sad since great programming skills and great design skills tend to be mutually incompatible skill sets.

HTTP: ubiquitous but too limited by the stateless 'request - response' model. WebServices: as bad as HTTP. OLE::COM: way too complicated, and not platform independent. CORBA: same problem as OLE. XPCOM: complicated, and does not seem to be catching on.


In reply to Re: GUI with HTTP::Daemon by dimar
in thread GUI with HTTP::Daemon by Juerd

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, 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, 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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others cooling their heels in the Monastery: (5)
    As of 2019-06-20 02:49 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      Is there a future for codeless software?



      Results (89 votes). Check out past polls.

      Notices?