Node.js Technical Steering Committee, 22 Aug 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Node.js Technical Steering Committee meeting - Aug 22 2018

Description

https://github.com/nodejs/TSC/issues/580

A

Okay, well welcome to the no GS technical steering committee meeting for August 22nd 2018 following our standard agenda as per the issue. So, first of all the does anybody have any announcements they'd like to share.

A

You know if we don't have any announcements, then, let's move on to the items tagged in the with the TC agenda. The first one is number two, two three five to stream. What WD g WD streams jeremiah did propose in the issue that we defer that to next meeting so that he has time to comment in the issue because he's invested in I. Guess you know having having work on the new streams he's invested in that and has a number of comments he'd like to make just has not a chance to do that.

A

Yet so I think that makes sense to me unless anybody else thinks we need to discuss it this week.

A

Okay, so let's move on to the next issue, which is FS feature detection for recursive mcdr. This is two to three zero. Two I'm just going to open that up and we'll see if we have the person here who added it to the or if you, if you are the person who added it to the agenda, speak up.

A

So I guess miles added it to the agenda. In this case, I did look at it briefly early on it's it's talking about now, feature detection and you know, there's a proposal for how to detect specific features, but there's quite a discussion going back and forth see is anybody here have been particularly active in the discussion.

A

I I have I, followed it. Okay, so do you want to give a bit more of a framing or.

B

You probably know that we have landed on master the ability to create a directory directories recursively there.

C

B

Also implemented in C++ and is like 30% or more faster than Hospital, and everybody is acting with that API. However, that API has been landed with an option as an option of standard mcdeere and.

B

And the problem is that by using an option, it's impossible to feature the taxes. So basically there are a couple of techniques suggested, but it's.

B

No not really feasible and useful and usable. So that's kind of the current problem now Myles proposes to add this feature called this new symbol called util dot features I discuss with him a bit. I am not necessarily agreeing on on the way the symbol is used, but that's a different story.

B

Basically this symbol, and this is basically what what it was it enable our application to know. If the result is this or not, this approach is: it has been pushed back way by some individuals and to the point that we haven't. We have to make gear from landing in.

B

From landing in core in a firm landing in no time the program steers about the fact that you know you can use, because it's basically a new pattern, complicate things and so on and so forth and I haven't done. A lot of this myself is very hard to to get this thing. No reason why miles pings the TSE here it's because he would like to see if we agree on the process of using that symbol to do feature. Detection are on a function. Log right.

B

They argument against. That is. We should strive to not have to rely on that.

A

Right, okay, it sounds like like, unless people have strong feelings on it at this point, maybe we can take it back to the like. We don't I, don't think we have enough of the active participants here to really come to conclusion. So maybe we should push it back to github for a week and then discuss again.

B

Like this is I, I do agree genetically so that the argument is we should. We should not be big deer, but should have been a function to make me of pee on the NFS system. So.

B

Yeah, what are less, this I'm.

A

Okay, so I think I think it's you know unless anybody else has does anybody else have some things they want to add to the conversation today.

A

Right, okay, so rich commented that you know he's he's also in favor of make your P, but we need the you know miles to close it out. So, let's defer to next to get back to github and, if necessary, just discuss next week when we have miles in the call perfect.

D

A

Okay right, so the next issue is process resolved, swallowed event to to to 1/8.

A

Me up that one.

D

Who are attached.

A

B

Rubin added it so served by Rubin. There is this is where there are two alternative implementations between this and.

B

The one from ethnic and basically I think the question is what to do.

A

Right, I guess it's around the yes.

B

So this event is is needed for the bugging promises reason so I would invite both I agree with reach. That proposal invite Rubin and goose next week to present the case substantially. The API is the and the implement the same thing more or less in different ways, and they both disagree with each other they from a user perspective. They are very similar, so.

A

Basically, we can say they're very close, but not reaching consensus, let's see yeah so okay, so we can basically actually consensus.

B

We need a champion to gather all opinions and everything about this.

A

Okay, that's sometimes.

E

A different issue so the further the next week and invite no no it's this issue. Sorry, sorry.

A

Okay, so ice. We need to do what it did for okay to do for that. What you did for scoping right, yeah.

B

That is a champion for this and helps in resolution, and somebody that is not.

F

And doesn't have a vested interest on on this right. Do we have a volunteer from anybody who's here, I.

B

Can't because Romans are clean, so I.

A

Guess I'll take the action to send out an email.

B

I can do it. Oh.

A

Okay, great thanks for Shh.

D

D

Rho2 soon right.

D

A

um So, which is gonna act as like this champion together.

D

A

You don't expose promise events, so that's the next issue, which is 2 1.

C

E

C

E

A

C

F

A

Issue this one, yes, okay, great password, hashing API, is two one: seven, six, six I.

A

Know Chalker III, yeah, I seed I've tried to promote chakra I still don't seem in need, like I, see one attendee but he's not eating the attendee list. So I haven't.

F

A

Able to do that.

A

C

A

A

Okay, so basically the key just commented that no updates, yet so, let's defer so that's okay,.

C

A

Next, one is two one: six five four make wreaths make underscore read: throw error, TTY writable, not readable, as.

B

These has reached consensus, so I can talk about briefly about it, but unretire there objection, okay. The reason that is the situation is that we libuv add, so we were using an API run from libuv and causing some side effects on the node side, meaning that somebody could read from standard output, which sounds a little bit weird, but that was what was available and they basically have made that track more strict, okay.

B

Unfortunately, this means that we can't have any more did we can't read any more from standard output from using libuv, using without a libuv API change or an API breakage, a new API or an API breakage, which doesn't look, and there is that has been. This has been an issue open on the libuv side and now no real movement for the last weeks. Right.

C

B

The last two three weeks give me some discussion, but it doesn't seem like there is any buried, however, who they are users that are using been using that API I've, faced with a very, very bad error, so like something Enoch, Khan or Suns, like that, where is very, very hard to debug, so I'm given to know, what's what's happening, what's going on right.

C

B

Yeah I am going to land this with the idea that if we get back that feature, we will revert.

A

Okay, if slip UV updates in time, so basically, okay,.

E

So you're gonna land and will revert if yeah well. It is.

B

Not in the one give if you, if we get that feature from libuv but I, the current, the current situation seems unlikely that it will happen in a matter of weeks right.

B

So that is at least my understanding. Okay, I see no movement code ones. So, okay,.

A

And this is sound like this. If nothing just makes a situation better right, yeah these.

B

These doesn't fix the problems these just avoids this just show. People are viajero that you know they shouldn't do this like reading from standard output. Even if it's possible is this something that somebody should be doing right.

C

Like yep, okay,.

A

Any other discussion or comments before we move to.

B

Their mic Alaska can we land in a similar patch and we so it's technically, it's a neighbor code change. So it's summer major, but I will open up a purifier, Syntagma G STS C and we could use our full powers to actually put it down. It was a bad time, but I I put it in as assembler major because it technically is as information, but it was a semi major, even updating. Maybe we breaking back.

A

Okay sounds good, just taking the notes to that effect. Yeah. Any other comments, questions before we move on.

A

No: okay next issue is buffer, a runtime deprecated buffer constructor everywhere by default.

A

Opening that one up.

D

A

Write this one went back on to the TSC agenda, just seeing if there's any new discussion.

A

See Trek rich definitely has commented.

A

So I guess witches suggestion is that you know really we're pretty much at the point where we should take a vote. There is a request chakra or if anybody else could provide the data of any relevant data about the constructor usage in the ecosystem, I think otherwise, rich I guess you're suggesting. Maybe we just call a vote at this point. I get that data and then call for a vote.

A

Almost anybody else think in terms of so Nick Nikita has commented that he has made a proposal 2135 one and that you know basically, he would like some comments on that as an option.

A

So I guess you know what my recommendation would be. Is that you know? Maybe we allow this next week for discussion and we schedule a vote at the next meeting. If we do not have consensus by then.

A

Okay, so I'm just going to take notes, leave this week or discussion, but schedule vote.

A

So rich, are you suggesting we need to do that before next week,.

A

Just responding yeah, so I I'm, adding it in the minutes. That's okay! You know leave this week for discussion, but schedule vote for next week. Is that what you wanted, the minutes or something more?

A

Okay, he's going to type in two minutes.

G

Can can you hear me yep? Okay, so what I want to type or say what I want to appear in the minutes? Is that what I don't want to have happen is have us, kick it back to github for a week and then call a vote, and nobody has thought about this, because that seems to be the running theme of everything that's been on the agenda today.

G

Is that where nobody's prepared to talk about it- and this is an important issue that needs to be decided in the timely fashion because it needs to go in a release and we get the word out to the community if we're going to do this, I personally suspect that we're not going to do this and that's fine, but if we are going to do it, the decision has to be made soon, and the word has to get up quickly and we can't like push this to get up for a week.

G

Have nothing happen and come back next week and be in exactly the same place where we are now. People need to actually, like you know, look at this and come to their conclusions about where they stand on it. I.

A

Guess the alternative is, we can call for a vote now finalize the vote in the meeting next week. If that is any I've said, I have.

G

To say- and you don't have to put that in a minute so to get that out there, okay.

A

Okay, so strong call for everybody to you know, review, weigh in make a decision and we'll plan to close.

B

It out next week.

A

Just think anybody else have any other comments on that one before we move forward I.

B

Don't think we should do it, but that's my take.

A

Yeah I think I'm, that's the way, I'm leaning as well, and all comments in the issue this week, yeah.

G

If you, if you already know which way you're leaning, if you could put that in the issue that will definitely but I think when the vote happens, so that's a good thing to do.

A

Okay, the next issue, then, is update the Charter 569.

G

That one's mine I'd prefer to defer it.

A

Okay, next week, possibly two weeks out, okay.

A

Okay tracking issue for updating the TC on board meetings. We don't have miles so skip strategic initiatives, let's just quickly flip over to that.

A

A

So, okay, sorry I'm gonna have to be able to look at two things. At the same time, so HTTP we don't have James, you don't have I'm, just gonna go down the list until we have somebody who's here, so MEP I still focusing on Docs, but we're pretty much almost done. They're planning out next iteration milestone, milestone next milestone, which will focus on fleshing out tests and a few other things.

A

Including, of course, continued evangelization.

A

Okay, next in the list is open us, so we don't have rod workers errormsgs joining anything new on the air messages front.

A

Is is it just still moving ahead or is there like in terms of the C++ messages? Is we making progress or is it and just nothing.

H

Much progress, lady, okay,.

A

Core promise, apos governance James sure not here, v8 currency.

A

So I think Michael right, okay, so no update there, people have two people on holidays and stuff. We don't have Ali or miles okay, I! Think that covers what we can cover on that front. So that takes us to the end of our regular agenda. Does anybody watching on the stream have any questions.

A

Anybody have the stream up.

A

Okay and find that then.

A

Okay, I'm just looking now for work, questions, I, wear.

C

I want this convention. One question: does Facebook hire no just developers, I, don't think.

A

That's a question that I don't know: I can't answer that I don't know if anybody else is on the call can answer that. Okay.

A

I guess we don't know, I think it would have to be a good question for one of the contact pages or something like that on Facebook. Was there any other questions we saw there Gabriel.

C

No, this is the.

B

Only one and.

C

It was forwarded to us by Francisco, okay.

A

A

Okay, so I guess, if that's the end of the questions, we will call it for the the meeting for today, thanks to everybody who took the time to come out and participate and listen and we'll talk to you all next it next week, hi, okay, I'm gonna turn this off.