8 ms·
URLs are the uniform way to locate resources
- jacquesm 16y agoIsn't this kind of obvious ?
- bradgessler 16y agoYes, but sadly this often gets overlooked. database.yml in Rails is a great example of that.
- catch23 16y agoThough sometimes it is nice to separate things out. Back in the java jdbc days, I'd always have to look up the exact url format for database connections because oracle's url connection string would be completely different from mysql, and still different from postgres.
- rbanffy 16y ago> because oracle's url connection string would be completely different from mysql, and still different from postgres And that makes sense. At least a little. Because the way you use to locate a resource may vary wildly between databases. And mind you we are only talking about relational ones (the kind JDBC cares about).
- vsync 16y ago> And mind you we are only talking about relational ones (the kind JDBC cares about). It gets even more fun with Java EE where you can have arbitrary resource adapters. So then you have even non-SQL naming conventions to map within your application server.
- Legion 16y ago>> "Why don’t we use this format for locating Git resources?" Because everyone is already doing what your article is telling them to? I'm sure there's a point to the article, but I found it strange that this call-to-action style post showed numerous examples of how this is already being followed, but only one - completely fictional - example of not following it.
- jacquesm 16y agoWith the number of upvotes it is getting I am wondering if I'm missing something. There must be some amazing revelation in there somewhere.
- georgieporgie 16y agoAll I can figure is that some portion of the young hacker crowd grew up with such ubiquity of URLs that they never reflected on the meaning of the name. Or bots.
- jacquesm 16y agoLet's help them along a bit then with some real info instead of this watered down errm... stuff: http://www.faqs.org/rfcs/rfc1738.html http://www.faqs.org/rfcs/rfc1738.html Which has since been superseded by http://www.faqs.org/rfcs/rfc2396.html http://www.faqs.org/rfcs/rfc2396.html and in turn by: http://www.faqs.org/rfcs/rfc3986.html http://www.faqs.org/rfcs/rfc3986.html I think that's where we are right now, I might be wrong. Happy reading. Incidentally, the article refers to URLs, instead of URIs: http://en.wikipedia.org/wiki/Uniform_Resource_Identifier http://en.wikipedia.org/wiki/Uniform_Resource_Identifier URLs are a subset of URIs, the differences are subtle for the most part you can ignore the existence of URNs and pretend URL == URI but it is useful to understand how they relate and that there is a difference.
- andrewtj 16y agoYou and I both, especially since it's a repost http://news.ycombinator.com/item?id=1230768 http://news.ycombinator.com/item?id=1230768
- gjm11 16y agoPrevious HN discussion (a couple of months ago): http://news.ycombinator.com/item?id=1230768 http://news.ycombinator.com/item?id=1230768
- hackermom 16y agoTo be picky, it should be "URIs are the uniform way to locate resources", not "URLs" - software, web and general computer usage today extends beyond the typical scheme format of "protocol://address", f.e. handing out a Spotify URI to someone, clickable in their IRC client, or even directly pastable in their browser's address field: spotify:track:5IsPWc2uTiVINs3Lfn8s9o
- rbanffy 16y agoTo be even more picky, "URIs are the uniform way to identify resources" or "URLs are the uniform way to locate resources"