| 12:49 | <Stephen Belanger> | In Node.js I still see significant usage of |
| 15:27 | <James M Snell> | Because the original design of enterWith was quite broken. It’s better at this point, but still not recommended unless you know what you’re doing because it doesn’t work quite the way people seem to expect in some cases. enterWith(...) used it really wasn't necessary. A .run(...) would have worked just as well. It's one of those things that folks will use because it's available not really because it is the best tool for the job |
| 22:45 | <Stephen Belanger> | It’s necessary for APMs, unless they have a sufficient diagnostics_channel with runStores to provide a scope. At the time of its creation we needed it to be able to put http requests into a tracing scope without a closure that we could not provide without patching. It mainly existed to avoid costly closures which were a major performance cost to APMs which gave them non-viable overhead for a lot of customers. As async/await became more of a thing though their value resurged—async/await syntax really needs set semantics for context storage to play nice with it. |