They could cut it 110%, so my available RAM grew bigger, and I would still not trust them. They have been caught with their hands deep in the cookie jar too many times.
Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
211–220 of 289 posts
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#212I just found out Brave supports Vertical tabs, https://brave.com/blog/vertical-tabs/ I might have to try switching from FF...
Firefox has vertical tabs...
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#213It's getting harder and harder to main Firefox. Brave's split tab feature is simple but so brilliant.
A decade ago there was a Firefox addon called Tile Tabs that could do any number of arbitrary splits. It died along with all the old-style XUL addons.
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#214Earlier quoted context omitted.
> And yet Rust ecosystem practically killed runtime library sharing, didn't it? Yes, it did. We have literally millions of times as much memory as in 1970 but far less than millions of times as many good library developers, so this is probably the right tradeoff.
It's not just about memory. I'd like to have a stable Rust ABI to make safe plugin systems. Large binaries could also be broken down into dynamic libraries and make rebuilds much faster at the cost of leaving some optimizations on the table. This could be done today with a semi stable versionned ABI. New app builds would be able to load older libraries. The main problem with dynamic libraries is when they're shared a…
> I'd like to have a stable Rust ABI to make safe plugin systems
A stable ABI would allow making more robust Rust-Rust plugin systems, but I wouldn't consider that "safe"; dynamic linking is just fundamentally unsafe.
> Large binaries could also be broken down into dynamic libraries and make rebuilds much faster at the cost of leaving some optimizations on the table.
This can already be done within a single project by using the dylib crate type.
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#215It's getting harder and harder to main Firefox. Brave's split tab feature is simple but so brilliant.
1. Look for a new browser instead of Firefox that also have a history of being trustworthy.
2. Look at Brave - see 1.
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#216Is Brave actually a good browser now? Did they rewrite it or something? Last time I looked it was a janky JavaScript mess.
It's better Chrome: no ads, faster (because no ads), some nice features on top. What's not to like?
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#217Well brave still uses 300MB per tab on linux and almost 700MB per tab on Windows. So they do have a long way in front of them.
They're crushing it on ad-blocking. I love it for that reason.
Sure, but some like a trustworthy company from a trustworthy country behind the software we use. 45 MiB less isn't enough to forget the history of Brave. The hidden VPN install and adding their own affiliate links haven't been forgotten.
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#218Earlier quoted context omitted.
It does support dynamic libs, but virtually all important Rust software seems to be written without any consideration for it.
RAM is cheap mmmkay? Or at least it used to be when they designed the thing…
The problem is vulnerable dependencies and having to update hundreds of binaries when a vuln is fixed.
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#219Earlier quoted context omitted.
And yet Rust ecosystem practically killed runtime library sharing, didn't it? With this mentality that every program is not a building block of larger system to be used by maintainers but a final product, and is statically linked with concrete dependency versions specified at development time. And then even multiple worker processes of same app can't share common code in memory like this lib, or ui toolkit, multimedi…
> And yet Rust ecosystem practically killed runtime library sharing, didn't it? Yes, it did. We have literally millions of times as much memory as in 1970 but far less than millions of times as many good library developers, so this is probably the right tradeoff.
It's really bad for security.
Re: Brave overhauled its Rust adblock engine with FlatBuffers, cutting memory 75%
#220They could cut it 110%, so my available RAM grew bigger, and I would still not trust them. They have been caught with their hands deep in the cookie jar too many times.
Meanwhile Firefox keeps undoing its own track record. There really is no perfect solution to browsing the web these days.