Graduate WHATWG Streams from Experimental? #40950
Comments
|
I would add #39316 as well. |
|
I don't think they've seen enough usage and adoption and I'd like us to be able to change them before we do. I don't think there is rush to graduate them yet (is there?), I suspect once the community uses them more we'll uncover issues that might require breaking changes (in errors or API guarantees) and I believe that graduating them doesn't get us much and costs us the ability to make changes without long deprecation cycles. |
How do we make this happen? i.e. more people uses them. |
|
@ronag I think we just wait and also ship other experimental APIs that use them? We can also reach out to the community and explicitly ask for feedback |
|
I think we could just drop the console warning on them and keep them as experimental in the docs (the same is true for Blob, File, etc..). |
The API is still experimental, but the warning isn't necessary any longer Signed-off-by: James M Snell <[email protected]> PR-URL: #40971 Refs: #40950 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
The API is still experimental, but the warning isn't necessary any longer Signed-off-by: James M Snell <[email protected]> PR-URL: #40971 Refs: #40950 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
The API is still experimental, but the warning isn't necessary any longer Signed-off-by: James M Snell <[email protected]> PR-URL: #40971 Refs: #40950 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
The API is still experimental, but the warning isn't necessary any longer Signed-off-by: James M Snell <[email protected]> PR-URL: #40971 Refs: #40950 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
The API is still experimental, but the warning isn't necessary any longer Signed-off-by: James M Snell <[email protected]> PR-URL: nodejs#40971 Refs: nodejs#40950 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
The API is still experimental, but the warning isn't necessary any longer Signed-off-by: James M Snell <[email protected]> PR-URL: #40971 Refs: #40950 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
PR-URL: #42225 Fixes: #40950 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Mestery <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Geoffrey Booth <[email protected]>
PR-URL: nodejs#42225 Fixes: nodejs#40950 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Mestery <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Geoffrey Booth <[email protected]>
What else do we need to make sure gets done before graduating the WHATWG streams implementation from experimental?
/cc @nodejs/streams
The text was updated successfully, but these errors were encountered: