Joyee Cheung

> We used to have a build hidden somewhere but it is no longer built with more recent versions of Node. I think that is because the CI broke e.g....

> Obviously ,this still becomes a breaking change because individual isolates will have the imposed 4 GB limit but with pointer compression this is far less of a limitation than...

@laurisvan Pointer compression has already been a configure-time option that is disabled by default for years, though that the configure-time option has recently been broken by (likely) recent V8 changes,...

> However, once you decide to actually use the C++ addon from Javascript, you'll face "external ArrayBuffer is not allowed" and other surprises. I think the ArrayBuffer issues comes from...

I took a look and built upon the idea in https://github.com/nodejs/node/pull/47452 - but still block on kUserBlocking tasks (which is also what the documentation suggests, IIUC). That seems to make...

I changed https://github.com/nodejs/node/pull/58047 to only ref this issue instead of closing it, because I think that PR only eliminates a subset of the deadlocks, but not all - it may...

> Basically we'd need a process.diligentLoad() to load all lazy things from Node.js Not sure if I am following what this suggestion is, are you talking about something similar to...

> I've never run an application with globalThis frozen or with frozen intrinsics, as many things break. I have seen apps using it but it's not for defending untrusted code,...

> I mean a call that loads all the lazy-loading this in Node.js core into globalThis. I think you can practically get it done by iterating all the public builtins...

Back in 2018 at one collaboration summit I proposed to revoke the commit bit if it has not been used to commit anything in 3 months: https://github.com/joyeecheung/talks/blob/master/node_collab_summit_201805/core_collaboartors_status_and_scope.pdf (when I investigated...