Google Chrome Team: We are disabling RTTI in our builds because it adds 10-20% to the size of the final binary and that overhead is too much.

[david_chisnall@infosec.exchange]

Google Chrome Team: We are disabling RTTI in our builds because it adds 10-20% to the size of the final binary and that overhead is too much. Download times and installed disk space are really important.

Also the Google Chrome Team: We’re going to bundle an LLM with the install. Sure, it’s ten times the size of the whole of the rest of the browser, but I’m sure it’s fine.

[mariusor@metalhead.club]

@david_chisnall as far as I remember Firefox also bundles an LLM with the install (useful at least for in browser translations) but it still manages to keep the size reasonable...

[david_chisnall@infosec.exchange]

@mariusor

I think the Firefox translation models are downloaded on demand, the first time you request on-device translation from a specific language. Each language pair is about 60 MiB.

These are an amazing piece of engineering. They’re designed so that they can be trained on a single (powerful) desktop and they’re trained from corpora that are specifically built (and licensed) for improving machine translation.

[mariusor@metalhead.club]

@david_chisnall ah, I see, I missed that somehow, but it makes total sense.

[mariusor@metalhead.club]

@mkljczk it does, it does: https://support.mozilla.org/en-US/kb/website-translation#w_how-do-i-enable-the-translation-panel

@david_chisnall

[david_chisnall@infosec.exchange]

@mkljczk @mariusor

I really wish Mozilla would stop calling things like this ‘AI’ because it causes exactly the confusion that you’re addressing.