Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #40050
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Node.js: asynchronous input, and sequential processing |
| Date | 2021-05-13 17:49 +0100 |
| Organization | A little, after lunch |
| Message-ID | <s7jlbk$vco$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> |
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?
If I say
asynch function ... I create a thread.
--
"I guess a rattlesnake ain't risponsible fer bein' a rattlesnake, but ah
puts mah heel on um jess the same if'n I catches him around mah chillun".
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