Well, what problems are you trying to solve by having the classes all access each other’s data members? Why is that necessary?

Because I didn’t know absurdism, I read the second one differently at first:

[The] nothing matters.

And I immediately had to think of this gem:

“But it doesn’t do anything!” - “No, it does nothing.”

That may be true for smaller cities, but in bigger cities it becomes impossible, because there just isn’t enough space to house all the people near areas of interest. Cars don’t factor in there at all. Give me a subway for the major areas, and perhaps a tram or bus system so you don’t need that many subway stations in the residential areas, and you can have car-free city centers.

I don’t really like including pedestrians in there. Like sure, you can fit a bunch of people in a small area, but another point you shouldn’t ignore is the throughput over time, and pedestrians are by their nature rather slow. Obviously if you’re looking at shopping in a street lined by shops left and right, then that street becomes tailor-made for pedestrian traffic (and nothing else except perhaps bicycles). But public transport is much better suited for travelling any further distances, and that should be the main focus when deciding to ditch cars.

Late reply, but for me personally, I started doing it because my Keepass database is already accessed using two factors (password and key file). Therefore, I’d gain very little by keeping the second factor of those sites external - essentially, those second factors are compounded into the second factor for the database.