Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Mild Shock <janburse@fastmail.fm>
Newsgroups: comp.lang.javascript
Subject: Re: Difference between 3rd party and native [Confusion by Lawrence D'Oliveiro]
Date: Wed, 13 Mar 2024 14:06:43 +0100
Message-ID: <uss8d4$1a6on$1@solani.org>
References: <usquog$19ifk$1@solani.org> <1clu637150wl5.locsf12fk0z0.dlg@40tude.net> <uss6s7$1a5rg$1@solani.org> <uss81o$1a6hb$1@solani.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 13 Mar 2024 13:06:44 -0000 (UTC)
Injection-Info: solani.org; logging-data="1383191"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.1
Cancel-Lock: sha1:BYLyqhO1bAXbBbuK9EcrdQ3AeqU=
X-User-ID: eJwFwQkBwDAIA0BL5c2QQ6HxL2F3YSk58Iz0YLBbdXb1eRbhT+ZuWQ1Vqga1oSrhiJZzidsARuzg01xyf2BaFZ4=
In-Reply-To: <uss81o$1a6hb$1@solani.org>
Xref: csiph.com comp.lang.javascript:124301

So maybe we have found the first weak spot
in the feature matrice, where still a 3rd party
is needed. Namely a replacement for:

    XMLHttpRequest.responseXML

In my case for Dogelog Player, since there is
nowhere some support of XML, except for a
module library(markup) which supports creating

XML, but reading of XML is not in the scope,
I don't have any such requirement, to have
an isomorphic library that also supports

XMLHttpRequest.responseXML, so I am not affected,
by this gap in the isomorphism. But other projects
might be indeed affected. Anyway might post

should be read in the context I posted it. I
remarked for Dogelog Player, that it is now
fetch() everywhere. Which is possible since we

currently have no XML reading requirement.

Mild Shock schrieb:
> The internet is full of fetch examples, where
> some JSON is fetched and then converted into DOM.
> Thats the alternative world, alternative to
> 
> the world, where one would directly fetch XML,
> and add it to the DOM. The JSON might also come
> from a web socket. It implements a kind of
> 
> Model–view–controller
> https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller
> 
> At least if one indentifies the JSON with the model
> and the XML with the view. There are also many
> frameworks like angularJS that support such MVC.
> 
> But then there is svelte, which is more DOM based
> again. Pros and cons of fetch versus XHR is wide
> field. My choice of fetch isn't based on any of
> 
> such  comparison. All that counts for my choice is
> "no 3rd party dependence". But you can also
> more directly fetch XML with fetch(), like here:
> 
> async function display(){
>      const xmlFetch = await fetch("./yourXMLorXSL.xml")
>      const xmlText = await xmlFetch.text()
>      const xml = (new DOMParser()).parseFromString(xmlText, "text/xml")
>      console.log(xml)
> }
> 
> Which would be a replacement of XMLHttpRequest: responseXML,
> expressed in "direct style" programming with
> async/await. Not the promise/thenable hell with .then().
> 
> But DOMParser isn't natively available on node.JS right?
> You would need a third party in node.JS?