Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%

Re:Brave overhauled its Rust adblock engine with FlatBuffers... by no_wizard on Tuesday January 06, 2026 @12:46AM (#46509136)

I don’t mean Dylibs like you find on macOS, I mean loading a binary lib from an arbitrary directory and being able to use it, without compiling it into the program.

It’s been some time since I looked into this so I wanted to be clear on what I meant. I’d be elated to be wrong though

[ Parent | on HN ]

Re:Brave overhauled its Rust adblock engine with FlatBuffers... by Groxx on Tuesday January 06, 2026 @01:05AM (#46509227)

Both handle that just fine. Go does this via cgo, and has for over a decade.

You do still need to write the interfacing code, but that's true for all languages.

[ Parent | on HN ]

Re:Brave overhauled its Rust adblock engine with FlatBuffers... by vlovich123 on Tuesday January 06, 2026 @01:45AM (#46509427)

Then by that argument Rust also supports dynamic linking. Actually it’s even better because that approach sacrifices less performance (if done well) than cgo inherently implies.

[ Parent | on HN ]

Re:Brave overhauled its Rust adblock engine with FlatBuffers... by josephg on Tuesday January 06, 2026 @02:23AM (#46509621)

Well, Rust does support dynamic linking. It just doesn’t (yet) offer a stable ABI. So you need to either use C FFI over the dynamic linking bridge, or make sure all linked libraries are compiled with the same version of the rust compiler.

[ Parent | on HN ]

Re:Brave overhauled its Rust adblock engine with FlatBuffers... by Groxx on Tuesday January 06, 2026 @01:46AM (#46509434)

It was built to do that, yes

[ Parent | on HN ]