Does supporting the Explicit Resource Management proposal hurt the ecosystem? #55342
Unanswered
JadenSimon
asked this question in
General
Replies: 1 comment 1 reply
-
The proposal is already at Stage 3 at TC39 and is available in Chrome, Deno, and probably more environments that I did not check. FYI - Node recently removed its polyfills. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
To preface: I'm not the type of person to create sensationalist discussions. My main concern here is the impact on the language and the developer experience, and I believe this needs more visibility.
By supporting this proposal, NodeJS is helping to entrench a feature that the author himself acknowledges is less valuable, compared to an alternative, in its current state.
From the proposal author:
This raises doubts about this feature in my mind. If anyone has their own experiences regarding
using
, I would really like to hear it. This is something the community should weigh in on. I personally found it to be clunky and confusing, especially with closures. I was very surprised when I found outusing
basically breaks with closures.Beta Was this translation helpful? Give feedback.
All reactions