Clean URLs are the backend or interface

Question

Do you think clean URLs are a backend or a discipline interface

Answer 1

If we say that the url is "clean" from the end user, then I will break the mold a bit and say that the url is not intuitive at all, and they will never be, they are designed for a machine readable.

There is no standard for the format of the URL, so when navigating from site to site, people will never remember how to reach a resource only by remembering URLs and their "friendly syntax". We can argue about whether '?' and '&' or '/' to express how to define a resource using a URL; Is one method better than another? it does not matter. At the end of the day, the machine analyzes it and sends the result.

We must stop fooling ourselves with the fact that people actually introduce these things and understand that uri are for cars, not for people.

I still need to use / remember a uri that goes beyond the first few characters of the http://domain.com/ part of the address and I have been using the network for a long time. For which bookmarks. Nowhere on the website does it say that “change this part here in our URL to view” any other resource, because the url is usually undocumented and opaque.

Yes, make your uri SEO friendly (hell even if they change periodically), but forget about all the "human / clean" information about the resource identifier, this is a mystical pipe dream.

I agree with Vlion that the url should provide a unique mechanism for bookmarking the resource and returning to it (unlike some of these disgusting web 2.0 ajax / silverlight / flash creations), but the bookmark will never be for people to understand and To understand, It seems that quite a bit of concern and energy spent on dreaming about URL strategies that people can remember and enter is a waste of energy. Let me get up and solve real problems.

Sorry for the pomp, but there is a lot of nonsense on the Internet related to URLs that occur in certain circles that are just a waste of time.

Answer 2

Now that Firefox Awesome bar and Google Chrome Omnibox Addresses can be used to search your browsing history, which makes it much easier for users to find their history for previously visited sites, so having clean URLs can help users find sites in their history faster.

Making sure the page has the appropriate name is important (since both browsers are looking for the name as well as the URL), but making sure the URL has the appropriate keywords in it when these keywords are entered in the address bar, the URLs will be more likely to appear in offers, as the keyword will be matched twice in the URL and title.

In addition, as soon as the user types the site name, they will be presented with examples of URLs from the site, which they can then use as a template to narrow their search. Therefore, the use of verbs and nouns in the URL for different sections or actions of the site will help the user narrow down their search to the part of the site where they are interested, for example, / questions / or / tag / sections stackoverflow or "/ doc" at the end of docs. google.com/doc, which can only be used to view document pages in Google Docs *.

Since Firefox and Chrome look for every word separated by a space entered in the address bar, it can be argued that there is no need to look for the URL to be completely understandable to the user, but to allow the user to really read the keywords they are interested in the amount of “noise” "should be minimized.

---

* which have the form http : //docs.google.com/Doc? id = gibberish

Answer 3

The answer is BOTH.

For example:

https://stackoverflow.com/questions/ 203278 / are-clean-urls-a-backend-or-a-frontend-thing

The number above is the database identifier. Chop off a nice part and it will go to the same page. Therefore, "are-clean-urls-a-backend-or-a-frontend-thing" is part of the interface.

Answer 4

My perspective is simple:

• every place I visit with my browser (with various exceptions for extreme cases) should be bookmarkable , and Forward / Back should be used, and not destroy data entry.

Answer 5

Beckens for sure. Your server is one that should take care of routing the resources requested by the URL.

Answer 6

I think the main reasons for using friendly URLs are:

• Easy to connect / share
• Presentation
• Seo

So I think this is just a pleasure from the customers. Although they are also good on the server, they are not critical.