It is an understandable design decision, and from an aesthetic standpoint truncating the URL does make sense.
My objection is twofold. One problem is that in my opinion truncating the URL limits the usability of the browser. Even though plenty of website do make a mess of anything behind the /, other websites and services do have understandable, bookmarkable URLs that aid the user in his or her browsing. Thankfully the URL is still a usable part of many websites, and modern Javasript frameworks too (traditionally the place where URLs were mangled for technical reasons) are now once again embracing proper and usable URLs (e.g., EmberJS).
Philosophically, I worry about hiding something as empowering and basic to the web as the URL. While I can sympathise with the notion that the path, query, and fragment parts of a HTTP URL are often technical details that may clutter the UI and confuse some users, I feel that hiding it is not in the spirit of the open web, and does not benefit users in the long run.
It is an understandable design decision, and from an aesthetic standpoint truncating the URL does make sense.
My objection is twofold. One problem is that in my opinion truncating the URL limits the usability of the browser. Even though plenty of website do make a mess of anything behind the /, other websites and services do have understandable, bookmarkable URLs that aid the user in his or her browsing. Thankfully the URL is still a usable part of many websites, and modern Javasript frameworks too (traditionally the place where URLs were mangled for technical reasons) are now once again embracing proper and usable URLs (e.g., EmberJS).
Philosophically, I worry about hiding something as empowering and basic to the web as the URL. While I can sympathise with the notion that the path, query, and fragment parts of a HTTP URL are often technical details that may clutter the UI and confuse some users, I feel that hiding it is not in the spirit of the open web, and does not benefit users in the long run.