Docs are less likely to be broken if GitHub implements some automated, global way to rename the main branch: when this isn't done in an ad-hoc, per-repo way, they can implement logic to redirect URLs.
(Or, for a quick and dirty fix, always redirect master to the main branch)
> I think a key aspect of remote work being successful is for the distributed team to be in the same time zone or have less than 1 hour time difference
I think the exact time difference doesn't matter so much as everyone can be at work simultaneously at least 70/80% of the time.
I'm very obviously not a lawyer nor lawmaker, but I'm under the impression that anything can be classified as an act of war as long as another country is willing to treat it as such, and other superpowers/blocs are willing to sign off on this assessment, and back it militarily and through sanctions/incentives.
(Though this would all probably swept aside as soon as somebody reverse engineers the vaccine.)
Maybe I'm overengineering, but couldn't you store the sanitized version as the normal value, and also store and make publicly available the original unsanitized value in an ominously and obviously named key (say, dangerouslyUnsanitizedValue) that happens to be easily greppable/lintable?
Hm... Features take some time to get to production. The stuff I use/appreciate most launched either before Microsoft acquired them, or shortly after the deal — so its development predates that.
In those places, old Apple hardware isn't significantly cheaper than new hardware. You might get a 25% discount for a degraded experience (security updates may end in ~3 years) or buy much older hardware (e.g. 9 year old models) that cannot run current macOS and Xcode, etc.
And yes, a local PC can work out to lower prices due to specific tax arrangements, sourcing components straight from manufacturers and assembling them locally.
Leaving common knowledge undocumented is, in itself, a misguided attempt at DRY.
Your common knowledge isn't necessarily everyone's common knowledge; what you perceive isn't necessarily what it is.
Every day there are many people just starting to code. There are cultural and regional differences. They might not have hit the exact spot in which this information appears.
Knowledge also disappears, fades, gets censored or destroyed, gets mixed up and remembered incorrectly. You might take something as a given and misremember it 20 years from now. You might read your own code 5 years from now and not know why something's there — something that was taken to be obvious.
Brotli has wide browser support (https://caniuse.com/#feat=brotli) and comes closer to zstd in compression ratio and compression speed, but its decompression speed is significantly lower and closer to zlib.
Not to gotcha this, but "I'm someone whose statements should not be taken to heart" is not a message I'd want to convey in an apology.
Then again, corporate communication is often a game of being as cynical as you can get away without getting arrested or having your business shut down, so maybe there's some meta-honesty here.
I would love a customer-company relationship in which the customer gets meaningful information by privately contacting the company with a polite message, but in my experience this is rare. When an answer comes, it tends to misdirect rather than tell the whole truth.
Here you have a bank and a company known for secrecy.
But you acknowledge this;
> random CSRs don't get a pithy explanation
What the throwers of hissy fits are pointing to is that, by building blackboxes, you can get whatever result you want (which doesn't mean all results are expected) with plausible deniability.
To put it shorter, with permission, liability stands with the organization; with forgiveness, liability stands with the individual. At worst, one or two levels up the hierarchy too.
> Both Firefox and Chrome support a common format for defining search engines from add-ons
...which have nothing to do with the Open Web, mentioned in the parent reply. Both require participating in, and consequently adhering to the terms of, stores operated by third parties.
https://en.m.wikipedia.org/wiki/Paradox_of_tolerance