Thanks to all who responded with their wisdom.

As part of this mission, I am studying the w3schools.com Javascript course. It looks like javascript is trying to borrow some good ideas from Perl in recent versions (e.g. use strict). Not surprising given some of its original atrocities. For example null versus undefined versus NaN - omg and I thought having to test (in Perl) with exists() instead of defined() was bad enough! So in terms of what should the host language be to encapsulate the child languages, javascript is definitely not a candidate, owing to the randomly contrasting decisions that were made about typelessness and values in its world (and the number of mobile app bugs I have seen created when data in new versions falls through the cracks in this system). The workaround (of multiplying up) to its having no 'use integer' pragma is particularly disgusting and unscalable and the lack of scoping just about bangs the last nail in its coffin.

On the other hand, arrays would be needed in Perl to represent XML sequences and I already had enough trouble having to maintain these for DHTML output from Perl (via sprintf) - one of the things that got me started with this. Python occurred to me as a more readable way to manage sequences, but was dismissed almost as rapidly when I realised the nesting depth is arbitrary and there is no syntax for dereferencing the nested structures (unlike in Perl and XML)

Looks like I am left with XML as the candidate host format in which to express the Perl, Javascript, HTML and CSS components of a web or mobile application. It has the added advantage of being able to plug in other server languages, like Java, PHP etc., although I may be tempted to compile that into binary XML before deployment. I still haven't given this mission the green light, though.

One world, one people


In reply to Epilogue re Maximising Language integration... by anonymized user 468275
in thread Maximising Language integration: Holy Grail or Dystopia? by anonymized user 468275

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.