Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jan Bruns Newsgroups: comp.lang.javascript Subject: Re: Synchronous XMLHttpRequest deprecated Date: 23 Jun 2022 08:46:32 GMT Lines: 20 Message-ID: References: <070420151603306966%timstreater@greenbee.net> <5523fc1b$0$2890$e4fe514c@news.xs4all.nl> <9585d114-082a-49b0-9c3c-185708e2a256n@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net /dEZ1kSRZRau+r3C1trs4gbwi0R+v0K1rDJsXvp0klOiOsttQL Cancel-Lock: sha1:UOJrsZMU1ovxQmMzI7xy+m3auoU= User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a git.gnome.org/pan2) Xref: csiph.com comp.lang.javascript:40920 The Doctor: >>Synchronous server requests are a perfectly reasonable thing to do in >>some circumstances. And I agree with the author that such a decision >>belongs to the application developer, not the browser maker. >> >> > Hence async. Ehm, What's the name of the JS construct to blocking-wait for signals? With more API calls becoming async-styled, the more difficult it becomes to collect related pieces of code in a block. And keeping deeply nestedd prenthesis in sync obviously also isn't very meaningful. And all this to make websites use up a complete CPU. Gruss Jan Bruns