There's a third benefit. In most complex programs, the engine is 10-20% of the code and the UI is 80-90%. Contrast that to most web applications, where the ratio is flipped. Flipping this ratio has another huge benefit - the LOC drops dramatically and time-to-market is cut in half (or more).
By using the browser as a UI, all I (as the developer) have to do is generate well-formed DHTML. Since I'm targeting a platform (IE, NS, MZ, whatever), I can even tailor my code to that specific platform. If I want, I can play nice, but I don't have to. Since the code is installed on the user's machine, it's more acceptable for the code to be tailored to that specific setup.
Yes, the goal is to flip the standard paradigm of DHTML. *shrugs*
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.