Repository navigation
async versions of slow libuv calls? #93
Description
Activity
Shouldn't
spawnalready be the non-blocking operation? Consideringchild_process.spawnSyncalready exists.If there's a way to make it more async, I'll be interested to hear that, I have attempted to come up with a promise API for child_process API, and couldn't find a design that made sense. If there's space for more asyncness, that'd be ideal for a new Promise API I think.
Shouldn't
spawnalready be the non-blocking operation? Consideringchild_process.spawnSyncalready exists.It is async in terms of IO, but it's not async in terms of computation.
Reacted by Rafael Gonzagasee nodejs/node#14917 re async spawn
If there's a way to make it more async, I'll be interested to hear that, I have attempted to come up with a promise API for child_process API, and couldn't find a design that made sense. If there's space for more asyncness, that'd be ideal for a new Promise API I think.
@aduh95 What were the design limitations or issues you faced?
- added 2 commits that reference this issue
on Jun 24, 2023 - added 2 commits that reference this issue
on Jul 3, 2023 - added 2 commits that reference this issue
on Oct 9, 2023 - added 2 commits that reference this issue
on Nov 26, 2023
e.g.
child_process.spawnandos.cpus()can be very slow calls that cause lag on the main thread. Would it make sense to perform async versions of these calls that run on a worker thread?