How do you fix that, when the process is literally "we throw an illegible blob at it and data comes out"? This is not even GIGO, this is "anything in, synthetic garbage out"

("But it works - when it works" is a tautology, not a useful model)

- DLC

- IRL

As in, "things that happened before my Xth year of life are Normal, nay, Traditional even. Everything afterwards is Ephemeral, and possibly Heresy as well."

Alas! All is ephemeral.

Only similar in the vaguest sense.

- vibe code a thing

- it doesn't work, but it was CHEAP

- hire someone "to fix it"

- actually means "rewrite most of it, but cheaper"

- also means "become the scapegoat"

To a developer, it offers most of the work for very little payment. Not an enticing proposition.

(Yes, I've been burned by various "it's 90% done, we just need a few fixes", and that was BEFORE the current slop era)

In other words, a singularly noisy pipe. (yeah, I know, it's going to be great as soon as it starts being great)

Thus, we get a built-in editor (less friction, yay/too rudimentary, boo) and popups (OSM events, yay/Popups are now everywhere, boo). And endless discussions on "this should be more/less prominent."

I don't think there's any official edict, but the approach "I don't like this and I'll make my own version" is at the very least workable (as opposed to, say, Google Maps).

Oh wait, that's not the disneyfied technooptimistic version of Luddites? Sorry.

(the name was a unique symbol)

Yes, all abstractions leak, there will always be edge cases. Doesn't mean "JUST USE ASCII DUH" (the lowercase extension is for the wimps); a whole spectrum exists between these extremes.