3 ms·
Hm, that's interesting; chrome://flags does seem to be titled "Experiments"... After, of course, you type "flags" into the address bar to get there. I guess I c
by yjftsjthsd-h 5mo ago
Hm, that's interesting; chrome://flags does seem to be titled "Experiments"... After, of course, you type "flags" into the address bar to get there. I guess I can see a distinction there, but it's pretty subtle.
- hnlmorg 5mo agoThis has nothing to do with Chrome. This is Go (golang). It’s not even the same language used in the development of Chrome. And the reason I make the distinction between feature flags and this is because some of the “experiments” discussed in the article are new packages / modules. So you’re not changing compiler behaviour via a flag or env var. You’re just importing a new package that isn’t yet considered stable.
- yjftsjthsd-h 5mo agoI think the way Google handles flags/experiments in one project (Chrome) is very relevant to interpreting the language around how they handle flags/experiments in another project (Go). And I'm pretty sure that their example is that importing "encoding/json/v2" doesn't work until you tell the compiler to enable it via environment variable.
- hnlmorg 5mo agoGoogle is a massive company and your json is example is literally a different module entirely!! I assume you’ve got experience in the subject you’ve got an opinion on?
- coldtea 5mo ago>I think the way Google handles flags/experiments in one project (Chrome) is very relevant to interpreting the language around how they handle flags/experiments in another project (Go). You'd think that, but you'd be wrong. Parts of Google can and do things their way. There's not an all-encompassing "Google way". And even if there was one, the Go team is notoriously doing things its own way.