Like most other readers here, my initial reaction is "Thanks, I hate it." I especially hate the assertion that they're increasing customization when in reality they've steadily been removing/hiding real customization options (e.g. compact theme, UrlBar.preventClickSelectsAll).
But, on further consideration I see the value. This feature isn't for power users. The goal of this feature is to increase chances that normal everyday users will make Firefox their daily-driver browser. For many people, having a custom colored browser will be a deciding factor to keep them using Firefox. This is why they didn't call it "themes", which is a techy word that would cause many people to gloss-over and ignore it altogether.
And, in reality, Firefox is still the most customizable browser for power-users. This feature doesn't remove userChrome.css, it doesn't stop users from editing thousands of options via about:config. It doesn't prevent hardcore power users from editing omni.ja to restore preventClickSelectsAll functionality.
So frankly, I hope this feature can help increase Firefox's market share by even a little bit. The more people using Firefox - even if they're not power-users - the better for the future of the open web.
Open source projects often fork. To take one such example, years ago X.org forked from XFree86. Both projects considered themselves implementations of the X Window System. Can you imagine if XFree86 supporters insisted that X.org not be allowed to use "X" in their name? If these supporters invented their own name for X.org, say "Zorg", made outlandish claims that "X.org" sounded offensive to them, and that they earnestly believed that "Zorg" was a better name for the project, even though no one in the project itself referred to it by that name. Would you not agree that those using the term "Zorg" in this example are using manipulative language?
Another way to look at this: the difference between small-blockers and big-blockers is a deep philosophical divide, much like what often occurs in politics. Imagine trying to have a civil political discussion with someone that has different political beliefs than you, and that person keeps using loaded terminology, rather than neutral terminology. You can imagine that under these circumstances, it would be increasingly difficult to keep the conversation civil, and you'd be well within your rights to ask your interlocutor to use neutral terminology. If they refused, it would be a reflection on their lack of civility, not yours.
Gold has had a widely agreed upon definition for thousands of years. Bitcoin is a ~decade old open source project with a clearly established philosophical divide between small-blockers and big-blockers. In other open source project variants, small name changes like adding/changing a suffix or prefix are common, why would Bitcoin be the exception?
Given that you accepted that BCH is the continuation of big-blocker's vision of the Bitcoin experiment, your comparison of it to gold-plated tungsten is flawed. BCH has a legitimate reason to exist. Your comparison might be more apt if BCH weren't born out of the block-size debate, but that's simply not the reality.
Ultimately, the market has spoken on this issue. The Bitcoin Cash name has been accepted as valid. It's not a trademark violation and it's not fraud akin to gold-plated tungsten. It's a legitimate continuation of big-blocker's vision of the Bitcoin experiment.
The term "bcash" on the other hand is quite clearly a pejorative and a transparent attempt to manipulation language. I'd expect better on a forum like this, but of course there will be some low-brow argumentation style anywhere you go. I'm frankly surprised you're still defending its use at this point.
I'm curious why you chose to use the term "bcash" to refer to BCH. No exchanges or mainstream projects use that term to refer to BCH. As far as I'm aware it's primarily used as a pejorative, so it seems strange that you'd use it here.
As far as BCH's additional value: I'd suggest researching the block size debate. This debate is BCH's entire reason for existing. This article [1] from 2016 by Mike Hearn contains a good primer on the block size debate itself. He ended up quitting development of Bitcoin, but others decided to raise the blocksize limit - with or without the majority, thus creating BCH. Succinctly, BCH is the continuation of big-blocker's vision of the Bitcoin experiment.
And likewise, BTC fees are also at a local maximum[1]. Unfortunately, nothing has been done to actually scale the BTC blockchain since the last bull run. Onchain transactional capacity is the same as it was 2 years ago (limited to ~400k tx/day globally). Major n^2 transaction validation bottlenecks still remain within the Bitcoin Core software. With no plans to address these bottlenecks and increase onchain capacity, the fundamentals of BTC scaling haven't changed at all since the last time the market went boom and then bust.
This issue is frankly far more important than the style changes they made. It's a muscle-memory issue that drastically affects daily usage. I was so desperate to restore the sane behavior of not selecting everything on a single click that I was recompiling firefox prior to discovering this workaround.
My interpretation is they're saying that Chromium's address bar code is complex deeply integrated with many other parts of the code-base (including many parts that interact with Google's search APIs). On the other hand, Firefox's address bar code exposes a simple javascript API. This means that making and maintaining custom modifications to the address bar is easier with Firefox.
I'm sure you've seen the infamous "tank man" picture, which provides direct evidence that the PRC rolled tanks into Tiananmen Square. The above picture isn't as iconic, but it shows what the PRC did with those tanks: they crushed and killed anyone in their path.
But, on further consideration I see the value. This feature isn't for power users. The goal of this feature is to increase chances that normal everyday users will make Firefox their daily-driver browser. For many people, having a custom colored browser will be a deciding factor to keep them using Firefox. This is why they didn't call it "themes", which is a techy word that would cause many people to gloss-over and ignore it altogether.
And, in reality, Firefox is still the most customizable browser for power-users. This feature doesn't remove userChrome.css, it doesn't stop users from editing thousands of options via about:config. It doesn't prevent hardcore power users from editing omni.ja to restore preventClickSelectsAll functionality.
So frankly, I hope this feature can help increase Firefox's market share by even a little bit. The more people using Firefox - even if they're not power-users - the better for the future of the open web.