`--birch-is-evening` > sets the birch ranker to assume it is evening for birch chip ranking purposes. i begin to suspect there might be a better way of organizing all this functionality
That’s when `—organize-functionality` gets added
Chromium has over 1600 command-line switches
11–20 of 47 posts
Re: Chromium has over 1600 command-line switches
#12`--birch-is-evening` > sets the birch ranker to assume it is evening for birch chip ranking purposes. i begin to suspect there might be a better way of organizing all this functionality
Google pivoting to the mulch business?
Re: Chromium has over 1600 command-line switches
#13Any insight into what —? could be?
Re: Chromium has over 1600 command-line switches
#14I wonder if services like Gmail have hundreds of feature flags at any given point.
They do: Borg (Google's internal orchestration system) is very, very flag-driven and it's commonplace for services to have hundreds or thousands. That's presumably how Chromium ended up the same way.
Re: Chromium has over 1600 command-line switches
#15`--birch-is-evening` > sets the birch ranker to assume it is evening for birch chip ranking purposes. i begin to suspect there might be a better way of organizing all this functionality
I've been nerd sniped and am trawling through the code trying to understand what this means.
Apparently there is something called a "Birch Bar" which I've never heard of, it seems to be related to calendar events... which, is weird as I have never seen a native calendar in chrome.
https://sourcegraph.com/github.com/chromium/chromium/-/blob/...
Re: Chromium has over 1600 command-line switches
#16All this and yet input methods still don't work on Wayland
Re: Chromium has over 1600 command-line switches
#17My favorite is the one that disables CORS... makes it easy to write local clients/tools that can get data from anywhere: --disable-web-security
Weren't we able to have custom frontends for facebook at some time?
Re: Chromium has over 1600 command-line switches
#18Former chromium dev here - I wouldn't be surprised if many of these are deprecated and just need to be cleaned up (removed from the codebase).
Re: Chromium has over 1600 command-line switches
#19It's actually even more. --enable-features takes a list of features, and --force-fieldtrials takes a list of field trials. And each argument of --enable-features can itself have "sub-features", so you can have syntax like --enable-features=CoolFeature:Widget/1/Bells/cow*
I don't know if the syntax for all of this is actually documented anywhere, but anything in chrome://flags seems to be plumbed through via --enable-features. You can see the syntax in chrome://versions?show-cmd-variations.
It would be cool if someone updated the autogen table to also include the list of available features and field trials.
Re: Chromium has over 1600 command-line switches
#20I had to use some odd Chrome command line arguments to keep a particular fragile kiosk-mode-like use of a prototype working long enough.
It worked for our purposes, but we feared an update might break it. I went to some effort to prevent updates outside our control.
(The command line arguments can be removed over time. Also, the behavior/correctness can change over time. I wouldn't expect all combinations of arguments to be tested in all future releases.)