It's interesting to ponder if it's just the low density (caused by "having too much land" to expand on) or other factors that deprioritise walking like this.

The status quo is nation-states in roughly their post-WW2 borders, and it's fiercely protected. The upside is stability and fewer wars, the downside is that the only way to try anything new is to co-opt an existing country. Adding to that, most countries are ethnostates that would prefer to have only a small percentage of their population be migrants. It's an easy way toward social cohesion, you just stay roughly where you're born, with people who were also born there and share the same cultural background. As we can see, it's not ideal - two lifelong neighbours can easily hold completely opposite moral values.

The US right likes to call their opponents pedophiles, but it would be ridiculous for anyone to adopt that label for themselves because of it.

Maybe if we wait long enough, the distribution of devices being manufactured will match consumer preferences, but I don't believe that to be the case today. The iPhone Mini sold ~millions of units. That may not be enough for Apple, but it's certainly enough to make a profit, yet nobody's building small phones now.

I'd be happier if this was something the market took care of, but after 10 years of glued-in batteries that you most likely can't even buy, I think it's time for a regulatory nudge.

I think it's fine to say C#'s data model is a superset of Java's or Rust's a superset of C's, but XML and JSON is too far for me, personally.

The obvious way is to use elements for everything, but then you're mapping both structs and their fields (very different concepts in e.g. C) to elements. Attributes map nicely to struct fields, but they only admit string values.

React is over a decade old, and as far as I remember, desktop apps using embedded browsers (Electron) started becoming dominant after it came out.

The ease-of-distribution advantage is huge, but web technologies are big outside the Web too, where it doesn't apply.

(Besides my main point, idiomatic web UIs don't implement resize handlers for positioning each element manually, but instead use CSS to declaratively create layouts. Modern GUI libraries with visual builders can also do this, but it was decidedly not the norm in the 90s. Also, modern dynamic GUIs generally don't use a static layout with disabled parts, but hide or add parts outright. That kind of dynamicity is hard to even conceptualise with a GUI builder.)

EDIT: I forgot to check the "removable battery" checkbox; with it you get zero matching phones. Maybe you should've checked that before assuming GP just can't search.

Not to end on such a negative note, foregoing a maimum height and the removable battery, Sony's Xperia 5 and 10 fit the rest of the requirements and are very good phones. Hard to find for sale in the last few years, though.

At some point, personal information becomes history, and we stop caring about protecting the owner's privacy. The only thing we can disagree on is how long that takes.