Anycast is hardly unique to Cloudflare. It's been around since the late 80s (before BGP), and has been used commercially for much longer than Cloudflare has existed. In fact, the root nameservers have done anycast for about 25 years or so and they're much more critical infrastructure.

Hence why in financial markets, a 10^9 billion is called a "yard" (from milliarde)!

Ironically, the cheapest phones available all tend to have Dual SIM Dual Active, usually because (in Europe at least) many have a second SIM card specifically for international calls.

So yes, it's "too expensive" because it's higher than $0, but it's not "too expensive" as in it would cost a lot.

Dual SIM Dual Active phones are under £100 in the UK, I imagine under $100 in the US.

Dual SIM Dual Standby (two or more SIMs, one radio) is cheaper, less battery, less space, and usually good enough. It's literally a few dollars, not 200-300.

Seems like I forgot to specify "5G" (those radios tend to be expensive) as the original poster was asking for an additional 4G/5G radio.

DSDA in 5G is rare, and I can't reliably find a phone that can do it in EU or US (I can find higher end chipsets that can do it, but phone vendors don't seem to follow through with it). Usually it's 4G+5G or 4G+4G.

Well, there's kind of a precedent at least...

> Gofmt's style is no one's favorite, yet gofmt is everyone's favorite.

Unlike formatting preferences, the colours I use in my editor don't effect others. That said I might not mind living in a world where everyone used the same highlighting scheme, as long as it was reasonable ;)

That's been a major success

It basically revolutionized the entire industry and thank god.

Opinionated standard formatting is now the default.

> Yet IPv6 hasn’t been adopted. For decades.

I'd argue it has, but that's not the point. IPv4 is pretty much mandatory for most users of the internet. Yes, individual users probably neither know nor core whether they're on IPv4 or IPv6, but it's so difficult to run IPv6-only that you just wouldn't bother.

Trying to teach someone about how to use ULA vs. GUA only leads to headaches. In fact, I'd go so far as to say the reason why the internet became so ubiquitous was because of NAT -- static internal addressing is pretty much fundamental to an easy-to-use experience. Having multiple addresses on a host only makes things far more confusing, so people don't bother, because IPv4 just works.

When I worked at OpenConnect (Netflix's CDN) there was a lot of Python too, and I started porting a lot of the tooling to Go. By the time I left (2019), Go was really starting to take off outside of OpenConnect too -- but yes, there's historically a huge amount of Java there.

A single PCIe-3 nvme drive will saturate it on a sequential read load.

Also a RAIDZ array (or just mdadm or BTRFS) with a cache in front can easily hit a couple GB/sec even on more consumer level hardware.

Needing to list an "executive sponsor" (an individual, not a role or a team) for each and every item in a service catalogue seems like mindless bureaucracy.

Meanwhile, having "custom properties" attached to each repo feels very much like administering JIRA, and schema-less YAML blobs that pervade the GitOps world.

Is it just me, or isn't the glaringly obvious solution to this an actual database and API, rather than just tacking on random bits of metadata that have no real-time validation etc?

As to the "executive sponsor" -clearly this is going to result in more "god" repos which keep accumulating responsibilities because nobody can be arsed to go through the official approval channels.

Source: my workflow once they required various TPS forms to be completed before you were allowed to create a new repository.

This is Microsoft we're talking about, they'd never do the glaringly obvious solution when mindless bureaucracy is an option.

Traditionally, that was the email address for the NTP service at various organisations, in the same way that postmaster was for the mail service.