Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #40053
| Path | csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | The Natural Philosopher <tnp@invalid.invalid> |
| Newsgroups | comp.lang.javascript |
| Subject | Re: Node.js: asynchronous input, and sequential processing |
| Date | Fri, 14 May 2021 09:15:50 +0100 |
| Organization | A little, after lunch |
| Lines | 21 |
| Message-ID | <s7lbjm$dbf$1@dont-email.me> (permalink) |
| References | <20210512110556.f2eb1917c4c2897f137dac40@g{oogle}mail.com> <s7gfop$r9h$2@dont-email.me> <20210513185907.882edb65b45a9c0317f19b08@g{oogle}mail.com> <slrns9qlsq.59j.jon+usenet@raven.unequivocal.eu> <s7jlbk$vco$1@dont-email.me> <slrns9qnv5.59j.jon+usenet@raven.unequivocal.eu> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=utf-8; format=flowed |
| Content-Transfer-Encoding | 7bit |
| Injection-Date | Fri, 14 May 2021 08:15:50 -0000 (UTC) |
| Injection-Info | reader02.eternal-september.org; posting-host="8b8545a3f7fed44fc421f04aec3fc5f0"; logging-data="13679"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/0C1ZFSDqpO4z9Gr4j+KW99rBI4AhUQww=" |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 |
| Cancel-Lock | sha1:xXuCS8Nosu7+SfooERxnM8WjuZA= |
| In-Reply-To | <slrns9qnv5.59j.jon+usenet@raven.unequivocal.eu> |
| Content-Language | en-GB |
| Xref | csiph.com comp.lang.javascript:40053 |
Show key headers only | View raw
On 13/05/2021 18:20, Jon Ribbens wrote:
> On 2021-05-13, The Natural Philosopher <tnp@invalid.invalid> wrote:
>> On 13/05/2021 17:45, Jon Ribbens wrote:
>>> On 2021-05-13, Anton Shepelev <anton.txt@g{oogle}mail.com> wrote:
>>>> The Natural Philosopher:
>>>>> seems you need multiple threads to do asynch at all.
>>>>
>>>> Why not? Cannot the same thread execute JavaScript-code,
>>>> state-machine code, and I/O-code?
>>>
>>> Pay no attention to this idiot, he has no clue at all what he's on about.
>>
>> Ok, what is a thread,. in *your* grammar?
>
> https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Asynchronous/Concepts
>
So, what I said...
--
Climate is what you expect but weather is what you get.
Mark Twain
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Node.js: asynchronous input, and sequential processing Anton Shepelev <anton.txt@g{oogle}mail.com> - 2021-05-12 11:05 +0300
Re: Node.js: asynchronous input, and sequential processing Jon Ribbens <jon+usenet@unequivocal.eu> - 2021-05-12 10:28 +0000
Re: Node.js: asynchronous input, and sequential processing Anton Shepelev <anton.txt@g{oogle}mail.com> - 2021-05-12 14:26 +0300
Re: Node.js: asynchronous input, and sequential processing Jon Ribbens <jon+usenet@unequivocal.eu> - 2021-05-12 11:30 +0000
Re: Node.js: asynchronous input, and sequential processing The Natural Philosopher <tnp@invalid.invalid> - 2021-05-12 12:56 +0100
Re: Node.js: asynchronous input, and sequential processing Anton Shepelev <anton.txt@g{oogle}mail.com> - 2021-05-13 18:59 +0300
Re: Node.js: asynchronous input, and sequential processing The Natural Philosopher <tnp@invalid.invalid> - 2021-05-13 17:35 +0100
Re: Node.js: asynchronous input, and sequential processing Jon Ribbens <jon+usenet@unequivocal.eu> - 2021-05-13 16:45 +0000
Re: Node.js: asynchronous input, and sequential processing The Natural Philosopher <tnp@invalid.invalid> - 2021-05-13 17:49 +0100
Re: Node.js: asynchronous input, and sequential processing Jon Ribbens <jon+usenet@unequivocal.eu> - 2021-05-13 17:20 +0000
Re: Node.js: asynchronous input, and sequential processing The Natural Philosopher <tnp@invalid.invalid> - 2021-05-14 09:15 +0100
Re: Node.js: asynchronous input, and sequential processing "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2021-05-13 09:53 -0700
csiph-web