Repository navigation
Call with V8 #454
Description
We had a few calls to sync between what was the CTC and select people from the V8 team in the past, with good outcomes.
I'd like to propose another one in the second half of January.
Some agenda items I have in mind:
- Update on GYP/GN
- GCC support in V8
- Visual Studio support in V8
- Snapshot support in Node.js
- Spectre and Meltdown
- Trace events
- Impact of
async_hooksperformance cliffs - General
Promiseandasync/awaitperformance considerations for Node 10 - Workers in Node.js
- Memory tooling
- REPL mode for V8 parser
- V8 extras
cc @bmeurer @ajklein @ofrobots @fhinkel @mathiasbynens @natorion
Before I set up a Doodle, I'd like to get a feel for the general opinion on this.
Activity
bmeurer commentedon Dec 22, 2017
I'd like to propose the following additions to that list:
async_hooksperformance cliffsPromiseandasync/awaitperformance considerations for Node 10cc @mlippautz
TimothyGu commentedon Dec 22, 2017
I think @bmeck would be interested in talking about a special parsing/execution mode for REPL, and perhaps about modules as well if there is anything. For that matter I’d be interested too but I’m not part of the TSC or a regular observer.
hashseed commentedon Dec 22, 2017
I don't think anyone would mind if we invite both @bmeck and @TimothyGu
bnoordhuis commentedon Dec 22, 2017
I have an in-progress cmake branch that I should get merged but it's currently blocked on nodejs/build#1003.
hashseed commentedon Dec 22, 2017
Even with the switch to cmake we would need a way for V8 to test against Node.js without having to maintain cmake configurations, so the GN wrapper still makes sense.
maclover7 commentedon Dec 22, 2017
Not sure if this is already documented somewhere, but I think having a more written down policy regarding support for VS2015 (is being dropped beginning in v10 IIRC?) would probably be good. IIRC, the change was related in part to things with V8
jasnell commentedon Dec 22, 2017
Count me in. Would love to see this happen again (and becoming a regular thing).
One additional item I would add is a status update on trace event implementation, just so we can keep it on the radar.
bmeck commentedon Dec 22, 2017
Sounds good to me.
mhdawson commentedon Jan 2, 2018
I'd like to attend as well.
hashseed commentedon Jan 4, 2018
Does it make sense to schedule before or after a TSC meeting? I would assume that that would be more convenient for TSC members.
mcollina commentedon Jan 4, 2018
We do have a calendar to schedule TSC meetings when everybody can attend, can we use the same system to schedule? What do you think @Trott?
Trott commentedon Jan 4, 2018
It's easy enough if we have the data. The challenge is getting everyone to enter data. Also, the TSC data is always for a Wednesday (UTC). Things get more difficult if you're talking about different days of the week.
For ad hoc meetings like this, I think Doodle might be more appropriate.
mhdawson commentedon Jan 4, 2018
@hashseed . My experience is that its always a pain to try to schedule a time. What I'd suggest is a doodle to pick the first meeting and then make agree on a regular time slot. It's easier for people to remember and less work each time. Depending on who wants to attend though you might need to agree on a few slots and rotate.
mhdawson commentedon Jan 4, 2018
I can see the rational of trying to piggy back onto the TSC meeting, but it runs long often enough and even if it does not people may be fatigued having it right after an hour meeting.
hashseed commentedon Jan 5, 2018
Okay. Assuming that most are located between Europe and West Coast, I chose european evenings and west coastal mornings for the Doodle: https://doodle.com/poll/d4ubsq5t6qczcdwm
Let's agree on a suitable time before the January 19th. Thanks!
21 remaining items
ofrobots commentedon Jan 31, 2018
video call is full 😿
cjihrig commentedon Jan 31, 2018
yes, what @ofrobots said
jasnell commentedon Jan 31, 2018
Ditto. Unable to join. Can we please pick something other than hangouts with higher capacity
mhdawson commentedon Jan 31, 2018
Going to setup a zoom instead
mhdawson commentedon Jan 31, 2018
https://zoom.us/s/157133358
mcollina commentedon Jan 31, 2018
https://zoom.us/j/157133358
devsnek commentedon Jan 31, 2018
is this no longer going to be streamed?
Fishrock123 commentedon Jan 31, 2018
We are live on https://www.youtube.com/c/nodejs-foundation/live
Fishrock123 commentedon Jan 31, 2018
The video recording is still processing but I'll post here when it's done.
jasnell commentedon Jan 31, 2018
Good thing you were recording because it looks like the zoom recording wasn't turned on :-)
Fishrock123 commentedon Jan 31, 2018
Youtube recording: https://youtu.be/a6YtLIaqMqs (Our stream settings are set to do archiving automatically.)
Fishrock123 commentedon Jan 31, 2018
@hashseed Think you could get us a link again to the clang presentation slides? I'd like to annotate the recording there.
Unfortunately I was not set up to record the actual video (and didn't really even think about it due to how our regular meetings are). That discussion starts at https://youtu.be/a6YtLIaqMqs?t=47m4s for like 20mins.
hashseed commentedon Feb 1, 2018
@Fishrock123 here's the clang presentation.
hashseed commentedon Feb 2, 2018
I created a summary.