Joyee Cheung

WIP in https://chromium-review.googlesource.com/c/v8/v8/+/4962094 to add in-isolate compilation cache support to `vm.compileFunction()`, locally I get ``` ❯ out/Release/node bench.js Running with Script took 56 ms Running with compileFunction took 55 ms...

The warning can also be temporarily disabled using `process.noDeprecation = true` (it's kind of an abuse because it's an experimental warning, not a deprecation warning, and it's kind of a...

FYI for v22.x the warning would be suppressed when the require() is coming from node_modules. For v23 we are considering the same but complications apply due to LTS policy https://github.com/nodejs/node/pull/55217#issuecomment-2488608261

> I registered a load plugin to get an exact count of the files loaded - it came out to 15312. The same exact count across multiple runs - exactly...

I suspect the load hooks might play a role in the strange behaviors you've seen here - the loader hooks are a bit all over the place and loading :...

> Is there a programatic way to persist the files? Or a specific exit code that will ensure it will wait? There is a WIP in https://github.com/nodejs/node/pull/54971 > Not super...

Actually I am not sure if the `>>> 0` part is needed for `zlib.crc32()` as the built-in version should always return a uint32 already. I think it's only necessary when...

The summit has passed. closing.

I left my machine that has macOS 13 + Apple Clang 14 now so can't provide more details until after the holidays but FWIW: when I tried to install the...

Also my 2cents: V8 uses (almost) tip of tree clang, so that's currently clang 20, and they have been doing a lot of C++ modernization that lower versions of clang...