2 ms·
Your arguments are definitely salient. However, I think there is something to this idea - a breadcrumb style approach by default in Chrome would encourage deve
by whoisthemachine 6y ago
Your arguments are definitely salient.
However, I think there is something to this idea - a breadcrumb style approach by default in Chrome would encourage developers to use paths in more standard ways that refer to resources, not heavy parameter coupling. As you noted, there are technical barriers to implementing this solution, which might encourage some other good things - servers providing resource discovery so that the browser can understand valid paths when visiting a site.
- wyattpeak 6y agoI address that in my point: Google deciding what paths developers should use is precisely what I don't want. I'll decide what resources should be discoverable on my site, not Google. I'll decide what paths should be valid, not Google. Google has too much power to dictate standards already, and has been quite happy to use that power for their own sake, rather than the good of the user. I'm not interested in giving them any more.
- sorenjan 6y agoMy original point was not about Google specifically, it was about a new feature in browsers in general. I absolutely agree that Google have too much power already. And like I wrote in my first post, the resource discoverability could be handled by the site itself via some manifest file in a standard format, like robots.txt. It wouldn't be dictated by anybody else.