profile
viewpoint
Anatoli Papirovski apapirovski Los Angeles, CA I do things & talk to people, a lot. Node.js Core Collaborator and TSC Member. Work @postmates (he/him)

nodejs/node-core-utils 117

CLI tools for Node.js Core collaborators

apapirovski/babel 0

:tropical_fish: Babel is a compiler for writing next generation JavaScript.

apapirovski/DefinitelyTyped 0

The repository for high quality TypeScript type definitions.

apapirovski/emotion 0

style as a function of state

apapirovski/end-of-stream 0

Call a callback when a readable/writable/duplex stream has completed or failed.

apapirovski/libuv 0

Cross-platform asynchronous I/O

apapirovski/node 0

Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:

apapirovski/node-core-utils 0

CLI tools for Node.js Core collaborators

apapirovski/node-templating-benchmark 0

Node.js templating benchmark (React, Nunjucks, ES6)

apapirovski/react 0

A declarative, efficient, and flexible JavaScript library for building user interfaces.

pull request commentnodejs/node

test: remove timers-blocking-callback

Sorry, I didn't say more earlier but I agree that this test is redundant. Tbh I've previously considered removing this myself so I'm strongly in favour of this.

Fishrock123

comment created time in a month

issue commentnodejs/TSC

Logistics of organizing a TSC summit to discuss the future direction of Node.js

Thanks for thinking this through @mhdawson — that seems a solid approach. Given the current lockdown, are we thinking we'll run this only during work days (Mon-Fri) or extend to weekends as well? I imagine there's obvious downsides to using the weekends but at the same time, we are far more likely to get good participation and engagement from everyone due to fewer conflicts. And since most people are sheltering in place, I imagine there aren't a ton of much better activities to do on the weekend...

apapirovski

comment created time in 2 months

issue commentnodejs/TSC

Review meeting date times ?

The 4 time slots + thu are way better for me. Too many standing mtgs on Wed that I can't move :(

mhdawson

comment created time in 2 months

pull request commentnodejs/node

src,http2: simplify native immediate queue running and harden http2 test

@addaleax Yeah, that makes sense to me. I guess that was the original crux of the issue — the naming ties into the JS setImmediate but the behavior only partially does. That said, I also don't have any great ideas re: naming. Maybe it's just a matter of adding a comment to the native SetImmediate function that calls this difference out?

addaleax

comment created time in 3 months

pull request commentnodejs/node

src,http2: simplify native immediate queue running and harden http2 test

@addaleax yup, I get that but the queues are somewhat tied to each other, right? Or well, at least I would expect them to be given the naming...

addaleax

comment created time in 3 months

pull request commentnodejs/node

src,http2: simplify native immediate queue running and harden http2 test

I missed this originally @addaleax but this seems like a semver-major to me, so probably shouldn't be backported? See https://nodejs.org/api/timers.html#timers_setimmediate_callback_args where we document the setImmediate behavior as:

If an immediate timer is queued from inside an executing callback, that timer will not be triggered until the next event loop iteration.

addaleax

comment created time in 3 months

issue commentnodejs/TSC

Logistics of organizing a TSC summit to discuss the future direction of Node.js

I'm wondering if it makes sense to make this a more long-running event — 1-2 weeks with shorter time slots and perhaps incorporating @ChALkeR's idea of having multiple sessions on each topic to allow people from different timezones to contribute.

apapirovski

comment created time in 3 months

issue openednodejs/TSC

Logistics of organizing a TSC summit to discuss the future direction of Node.js

Tying into https://github.com/nodejs/TSC/issues/797 and the discussion in today's TSC meeting, I'm opening up this issue as a discussion venue for how we can effectively organize a distributed event like this while allowing everyone from the TSC (and other interested parties) to participate.

created time in 3 months

issue commentnodejs/TSC

Nominating Shelley Vohr (codebytere) to the TSC

+1 🎉

Trott

comment created time in 3 months

issue commentnodejs/TSC

Nominating Matheus Marchini (mmarchini) to the TSC

+1

cjihrig

comment created time in 3 months

more