Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re: GUI with HTTP::Daemon

by dimar (Curate)
on Dec 19, 2004 at 00:09 UTC ( #415919=note: print w/ replies, xml ) Need Help??


in reply to GUI with HTTP::Daemon

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.


Comment on Re: GUI with HTTP::Daemon
Re^2: GUI with HTTP::Daemon
by elwarren (Curate) on Jan 06, 2005 at 17:10 UTC
    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).
    You're dead-on right about everything you've said, except this bit. I think the biggest hurdle is still the fact that developers create really ugly interfaces in html. Too much focus on functionality and not enough time spent making it pretty.

    Nobody wants to see an html page flash and render every time they hit a submit button, we want to a seamless clean interface that is just there and just works. Gmail is a great example.

    I personally have found that this is the biggest reason I like the google mail interface. It works like a real application. I click on a message and it comes up. I click on reply or forward and I can start typing right away.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://415919]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (7)
As of 2014-12-27 03:04 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (176 votes), past polls