Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!ecngs!feeder2.ecngs.de!217.188.199.168.MISMATCH!takemy.news.telefonica.de!telefonica.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <4006284.34SQex3vo1@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Tue, 28 Jan 2014 19:08:36 +0100 User-Agent: KNode/4.11.3 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <1fe2e508-cfc8-4933-997b-9bb462a2a593@googlegroups.com> <4250784.k5hfLq1mn1@PointedEars.de> <2748480.FELbIWn90F@PointedEars.de> <2158405.4KzAjcCDC7@PointedEars.de> MIME-Version: 1.0 Lines: 59 NNTP-Posting-Date: 28 Jan 2014 19:08:50 CET NNTP-Posting-Host: 9530f833.newsspool1.arcor-online.net X-Trace: DXC=FZXDZm8W4\YJN\YUVHKH;GI^WA:4gUTI10KQhadMDc@f1HP X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:22851 Michael Haufe (TNO) wrote: > [fallacies] > > Thomas 'PointedEars' Lahn wrote: >> Anyhow, even with your clarification I cannot find yours to be a sound >> argument. Yes, JavaScriptâ„¢ and all other ECMAScript implementations >> support the procedural-imperative, the object-oriented, and the >> functional programming paradigms. Obviously it supports the paradigm >> that is suggested (but not required) by the W3C DOM. How does that make >> it/them less suitable for using its features? > >> ISTM you have it backwards. All current DOM implementations *originate* >> from JavaScriptâ„¢ (versions 1.0 through 1.3), through the W3C DOM; not >> vice-versa. And there are ECMAScript Language Bindings *specified* for >> W3C DOM interfaces. > > Regardless of what the origin was, the evolution has been divergent ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > (though there has been efforts to improve this lately). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ What are you talking about? > The very fact that the term "interface" is used should be enough of a > starting clue of the mismatch. Again, why? 1. DOMs are specified using *interfaces* that are to be *implemented*. 2. Interfaces are a concept of, and are intended for use in, *object-oriented programming languages*. 3. ECMAScript *implementations* *are* object-oriented programming languages. Where is the mismatch? > Have the old arguments and discussions been > forgotten/overlooked? Is this mismatch honestly news here? Even an > off-the-cuff search will yield examples and arguments not yet mentioned: > > > > > > Throwing a bunch of URIs at people is no substitute for a sound argument. > ...and plenty of others if one is interested enough to bother looking. > Break out the bubble pl0x. The insularity is chafing ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Here we go again. -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.