5 ms·
I think re-ordering like that would actually benefit technical users more, but it's probably too late to make such a change. I don't think we'd need that change
by daveFNbuck 8y ago
I think re-ordering like that would actually benefit technical users more, but it's probably too late to make such a change. I don't think we'd need that change for browsers to put the parts they consider most relevant in bold. That logic is simple enough right now.
- basch 8y agoreally we are talking about rendering, right? not actually changing the protocol itself? (:lock: = lock unicode/emoji = secure http) :lock:/com/GOOGLE/www/maps/hawaii I am a strong proponent of the URL being part of the user interface. I should be able to manipulate what i request of a service by modifying the url. The text in the url should mean something.
- daveFNbuck 8y agoMaking the rendering that different from the actual URL would be very confusing, especially if it varied from program to program or within programs. Links would look one way on websites and then have a completely different form in the url bar after clicking them. That particular rendering choice would also have the downside of being the same for both https://www.google.com/maps/hawaii https://www.google.com/maps/hawaii and https://google.com/www/maps/hawaii https://google.com/www/maps/hawaii
- basch 8y agoYeah you might have to double punctuate after the subdomain, BUT it still makes it clear what domain you are on. https://com/google/www//maps/hawaii https://com/google/www//maps/hawaii And its not like the browser couldnt render it both ways, either on click or hover.