Alex Eagle

As far as I know, yes

I would hope that affordances for user customization continue to be plumbed through the directives-in-BUILD-comments scheme that gazelle uses already.

I'm hoping to convince @pcj who had some WIP on this at one point as well. Happy to discuss design more - my choices here were based on @achew22 suggestion.

Note: I noticed https://github.com/pluginrpc/pluginrpc which seems like it may turn into a better alternative to the hashicorp go-plugin, from our experience using the latter in Aspect CLI.

@thesayyn did some experimentation with WASM - I think that's an even shorter path to providing this kind of binary plugin support without needing to get protocol buffers involved. Very...

@blorente pointed me to https://github.com/tetratelabs/wazero - a pure Go WASM runtime with no need for cgo. @jayconrod I see you're active here recently. We'd like to contribute this feature in...

This isn't JS-specific, Bazel generally treats action inputs as opaque, checksummed files, and so if one action has a linux nodejs interpreter as an input, it will have a different...

I discussed this with @tjgq and there's an approach which is easy for us to try, I think of it as a "multiplex toolchain". Interpreter for all platforms are inputs,...

This came up at BazelCon this year in a talk on performance: https://static.sched.com/hosted_files/bazelcon2024/d0/TB-137%20Sharmila%20BazelCon%202024%20-%20Performant%20Bazel%20Builds%20for%20Web%20Monorepos%20at%20Scale.pdf I think it's time to implement this. Since it's breaking in theory when a program senses the...

Hey @jayconrod great to see you working on this - I was a reviewer for https://bazel-contrib.github.io/SIG-rules-authors/go-tutorial.html by @chrislovecnm (git history at https://github.com/bazel-contrib/SIG-rules-authors/commits/gh-pages) Should that tutorial be removed or updated to...