Yehuda Katz
Yehuda Katz
> But looking at the improvements you mentioned, it seems like they would also be received from any general WorkerNode + asyncAppend API. Can you point to any additional benefits...
> To make sure I am clear, the point here is that by proposing a separate API surface, we could exclude any operations that would be invalid coming from a...
> I hope I'm wrong, but this PR doesn't seem to be headed into that direction (yet?). @vlascik "(yet?)" is right. I'm trying to do this a little at a...
Is anything blocking this?
I think this is an ok thing to expose to build scripts, but it further highlights that a better factoring around build scripts might reduce footguns This kind of solution...
@DanCardin I'm a little confused. The justification I've always understood for using XDG paths is that you want to use the paths supported by the operating system, to facilitate things...
I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: - new features go through a public RFC that describes...
@cpojer I think we can do a lightweight version of an RFC process when we open source. The nice thing about leading with an RFC process is that it shows...
@KidkArolis indeed! I'm psyched that this ended up being the Yarn governance ❤️
I'm in favor in general, but really want to consolidate most of the runtime packages into a single published package first. I started work on that recently, but took a...