> That being said, I think developers have made some things more difficult to understand than they should be. While people understand what an address is, callin

> That being said, I think developers have made some things more difficult to understand than they should be. While people understand what an address is, calling it a URL adds an extra layer to learn (even if it is just terminology). URLs would also be easier to understand if they were more consistent from the end user's perspective, much like someone's mailing address, rather than an engineer's perspective. I really don't think they're more difficult than they need to be to be functional. Users' mental model of "an address" is incoherent and often context dependent. Both a URL and an email address are an "address" to most users. The really lost ones will refer to the search terms they use to get to a web page as the "address". I don't really see URLs as different from addresses. Their in descending size order rather than ascending like physical addresses, but the rest of it is fairly consistent. Most people spend drastically less time thinking about URLs than physical addresses though. We teach children how to break down physical addresses, and we do not teach them to break down URLs. It's entirely unsurprising URLs are more confusing. > It sounds like it makes things easier for the user. Yet all that it really accomplishes is creating confusion for the end user since it fails to differentiate two concepts. Phrased differently, it frees them from the requirement to be able to differentiate those two concepts. Much like how my calculator can give me the square root of a number without me needing to know how to actually calculate that.