Earlier quoted context omitted.
I was about to use a quote to show you that "no, it's not like what is described in the thread", but you included the salient bit in the second quote, yourself. It's not a gray area, and "opt-in" isn't something to be weasled-worded around. If the browser has the capability, I don't want it. I want to be able to add it with a plugin, and that's it . Plugins should have full control to whatever is necessary (same as a…
> It's not a gray area, and "opt-in" isn't something to be weasled-worded around How about "Translate" button?
And, if I'm being honest, "translation" is the only feature I would even consider splitting the builds for. At least in that feature I can see why a "default" version of the browser might benefit more people than not by including it. But that doesn't mean that a "clean" version shouldn't be provided. Build the core app, and then include as many plugins as you think "average users" will benefit from in the "default" version. I don't mind being the minority, I just don't think it's inappropriate to ask for only what I need instead of "all the bullshit you want to force me to have".