61–70 of 157 posts
The article's main insight: "URLs based on hierarchical names are actually the URLs of search results rather than the URLs of the entities in those search results".
Earlier quoted context omitted.
Doing this means that: 1) there are now an infinite number of URLs for every one of your pages that may end up separately stored on various services (mitigated for only some kinds of service if you redirect to correct), 2) if the title changes the URLs distributed are now permanently wrong as they stored part of the content (and if you redirect to correct, can lead to temporary loops due to caches), 3) the URL is now…
The usual way I've seen to deal with this kind of ambiguity is by doing a 301 redirect so that bookmarks get changed and the url in the address bar is also changed. It doesn't fix external parties linking to the site with the now deprecated url but there was never anything you could reasonably do about that. > If you are going to insist upon doing this, how about doing it using a # on the page, so at least everyone h…
Earlier quoted context omitted.
The notion of surfing the web without JavaScript enabled is increasingly antiquated. You can't even log into Google without JS enabled; it's necessary to mandate it because of iframe attacks.
Not all web pages are (or at least need to be) web apps. Logging into an account vs reading a static page is apples to oranges. Mandating JS to get any content, no matter how static, seems like the start of the death of e.g. Linked Data and a the web as an open standards based platform. I know I'm in the minority but diversity is a strength, and there are few places more important than the web.
Earlier quoted context omitted.
Cache invalidation remains one of the two hard problems in computer science (the other being naming things and off by one errors).
Off by one errors basically don't exist if you use modern languages and practices.
There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton https://martinfowler.com/bliki/TwoHardThings.html
"There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors."
The article's main insight: "URLs based on hierarchical names are actually the URLs of search results rather than the URLs of the entities in those search results".
In the most technical sense both are searches encoded in to a URI form. The search for the (hopefully) GUID just happens to be for a specific mechanical object, while the other is describing the taxonomic categorization of what a matching item would look like.
I didn't quite understand the point of the hierarchal "search URL" when you have the /search one implemented, and they go on to say you could implement both if you have the time and energy.
Earlier quoted context omitted.
The usual way I've seen to deal with this kind of ambiguity is by doing a 301 redirect so that bookmarks get changed and the url in the address bar is also changed. It doesn't fix external parties linking to the site with the now deprecated url but there was never anything you could reasonably do about that. > If you are going to insist upon doing this, how about doing it using a # on the page, so at least everyone h…
Minor nitpick, I'm not sure if exact match in URL slugs matters from Google's perspective very much. I do read that searchers' eyes can be drawn towards the exact match (which are frequently bolded in the SERPs), possibly leading to a higher clickthrough rate.
There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton https://martinfowler.com/bliki/TwoHardThings.html
There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton https://martinfowler.com/bliki/TwoHardThings.html
Aw, you didn't quote the best one from that page. "There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors."
It's worth including the third saying on the page just for completeness:
"There are only two hard problems in distributed systems: 2. Exactly-once delivery 1. Guaranteed order of messages 2. Exactly-once delivery"