<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2/7/2017 6:17 PM, John Carlson
wrote:<br>
</div>
<blockquote
cite="mid:CAGC3UEmAL8JJJeDv4WgwQMANgbQPhwmO8MfW=hjL47TRiQ1uuw@mail.gmail.com"
type="cite">
<div dir="auto">I guess what I'm referring to is the variety of
browser incompatibilities, along with the imperative style
impeding or stunting the growth of the declarative style.</div>
</blockquote>
<br>
John,<br>
<br>
I think that the browser incompatibilities in JavaScript are very
small, if there are any at all. That doesn't mean there aren't any,
just that it is likely not to matter to most (almost all) of the
functionality that is needed.<br>
<br>
There always be people pushing imperative over declarative (as the
other way around); but you don't see many people writing browsers
and lots of people writing web pages.<br>
<br>
There will be a dynamic middle-ground where some things are
declarative (e.g., models) and some things imperative (e.g., complex
user interactions). The middle-ground will shift as various
technologies and libraries fall in and out of favor or within
various domains.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAGC3UEmAL8JJJeDv4WgwQMANgbQPhwmO8MfW=hjL47TRiQ1uuw@mail.gmail.com"
type="cite">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">John</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Feb 7, 2017 9:12 PM, "Leonard Daly"
<<a moz-do-not-send="true"
href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div class="m_4324464715027322760moz-cite-prefix">On
2/7/2017 4:22 PM, John Carlson wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">So how are we going to provide a stable
JavaScript or vrmlscript environment with v4 X3D?</div>
</blockquote>
<br>
<br>
One way is to state that X3D uses HTML5 (see <a
moz-do-not-send="true"
class="m_4324464715027322760moz-txt-link-freetext"
href="https://www.w3.org/TR/html5/infrastructure.html#dependencies"
target="_blank">https://www.w3.org/TR/html5/<wbr>infrastructure.html#<wbr>dependencies</a>).
In there it specifies JavaScript as ECMA262 (<a
moz-do-not-send="true"
class="m_4324464715027322760moz-txt-link-freetext"
href="https://www.w3.org/TR/html5/references.html#refsECMA262"
target="_blank">https://www.w3.org/TR/html5/<wbr>references.html#refsECMA262</a>,
links to <a moz-do-not-send="true"
class="m_4324464715027322760moz-txt-link-freetext"
href="https://people-mozilla.org/%7Ejorendorff/es5.1-final.html"
target="_blank">https://people-mozilla.org/~<wbr>jorendorff/es5.1-final.html</a>).
<br>
<br>
That does not guarantee a stable JavaScript environment,
but it does identify who is responsible (HTML5 browser
writer).<br>
<br>
<br>
<div class="m_4324464715027322760moz-signature">-- <br>
<font class="m_4324464715027322760tahoma,arial,helvetica
m_4324464715027322760san m_4324464715027322760serif"
color="#333366"> <font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</div>
<br>
______________________________<wbr>_________________<br>
x3d-public mailing list<br>
<a moz-do-not-send="true" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>
<a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/<wbr>listinfo/x3d-public_web3d.org</a><br>
<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
<p><br>
</p>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>