But that's undefined behavior, so the compiler is free to ignore that possibility.

> so the compiler is free to ignore that possibility

And that's what is wrong. This is the most unfriendly behavior towards the programmer.

For context this article was written when 95%+ of websites used HTTP 1.1 (and <50% used HTTPS).

You must never drive on a curvy roads then. Every car I driven waits until the approaching car is fully around the corner, blinding them for a full second before dimming, instead recognizing the headlights around the corner and dimming earlier.

Newer cars with matrix LED headlights account for this, such as the Volkswagen ID series. The brights not only "blot out" the shape of the cars around you, they also rotate when turning or going around a curve, so that you never accidentally point them at oncoming traffic.

It's quite magical and weird to observe in real time. When driving past oncoming cars, you can see a halo of darkness around each car. There are videos on YouTube that show the effect pretty well.

I don't even know what a Chevy Bolt looks like! Maybe the problem is every other model.

It's not hard to know when a car is approaching from corners / hills; there's light before they get there. I have fun manually adjusting the brights; I drive automatic transmission, lighting is the only fun I get.

That's running 5 miles a day. Everyday. That takes months of training for an already fit young person to build up to.

90 minutes of extra walking is a lot of time to offset a snack that could be eaten in 1 minute.

That is just the run, though? My point in mentioning the other things is that it isn't that much, all told.

I also 100% think that your offset point is a big part of it. 90 minutes walking the dog outside is doubly beneficial because you are not snacking during the time.

The in-memory solution creates a 2nd copy of the data so 50GB doesn't fit in memory anymore. The kernel is forced to drop and then reload part of the cached file.

I actually can't tell. The majority of these are literally examples of bad regulations. They have mass appeal without care for 2nd order effects.

The top of the page is a banner rallying against a regulation that would fit right in on the page.

And the fact that the site is a laggy mess just makes it a bit surreal.

Despite the title, the article doesn't talk about "iffy internet" at all. It's all about "slightly slow" internet which is a complete non-issue except for large downloads (e.g. modern games).

Congested and/or weak wifi and cell service are what "iffy" is about. Will a page _eventually_ load if I wait long enough? Or are there 10 sequential requests, 100KBs each, that all have succeed just to show me 2 sentences of text?

I have two ADSL lines each of which is slightly below the federal broadband definition.

Most kinds of communication products (Zoom) work OK, except for anything from Google.

The dummy "loading" grey boxes it shows are still this size. Such a great "user experience."

"Is the parcel in the geographical bounds of the city name entered?"

The "city name" on an address isn't really a "city". SFO's address is "San Francisco, CA", but is not within SF city limits.

Queens NY addresses have "cities" that are just neighborhoods.

Applying any kind of logic to addresses will just be a minefield.

The Pentagon's address even has the wrong state. The address is Washington, DC, but it's in Arlington, VA.

i heard that is original secret underground metro system entrance location !

In much of unincorporated america, the most valid form of an address just uses the nearest city regardless of boundaries. Almost nowhere actually guarantees that every bit of land is even in a city limits. At the margins, addresses are unstructured free form text that is correct if it can be interpreted by a human with local knowledge.

There’s also no particular reason to expect that an address corresponds to exactly one parcel or that any given parcel has an address at all or that any given parcel has at most one address.

Yeah, this is bizarre. I don't know how it works in Canada but in the US the city/zip of the mailing address is just the location of the post office that delivers mail. It has nothing to do with the municipal the address is actually in.

hundreds of people in my city-county really think they live in a city in the next county over just because of the "city" label on their zip code

In some ways, yes. "Changing clocks" is the easiest it's ever been. We should be looking into changing them more often, not less. Two levels of daylight savings might be better than 1.

But on the other hand I think having the same sunrise time every day is actually pretty bad from a coordination perspective. Instead of everybody having a fraction of their year have an unfavorable sunrise, you will lock people into having either a light or dark commute.

Everybody will want to start their jobs at the same time making congestion worse. "Support jobs" (e.g. opening the store before "regular" business hours) will be permanently in the dark for their commute.