URLs: It's Complicated
netmeister.org
URLs: It's Complicated
1–10 of 41 posts
Re: URLs: It's Complicated
#2It seems like the colon is too ambiguous (is used as a protocol delimiter, delimiter for user/pass, delimiter for port).
Reminds a little bit of Java labels where you can do this:
public class Labels {
public static void main(String args[]){
https://hn.ycombinator.com
for(int i=0; iRe: URLs: It's Complicated
#3It doesn’t seem complicated at all. Complicated to me means difficult to understand. This just involves reading the spec and it all seems pretty simple and consistent.
Complicated doesn’t mean “new to me.” If I haven’t read a man page, that doesn’t mean the command is complicated.
Re: URLs: It's Complicated
#4Layouts using s are complicated too. For example, this page has a ~7800px-wide
tag in a that's 720px wide.
Re: URLs: It's Complicated
#5It doesn’t seem complicated at all. Complicated to me means difficult to understand. This just involves reading the spec and it all seems pretty simple and consistent. Complicated doesn’t mean “new to me.” If I haven’t read a man page, that doesn’t mean the command is complicated.
I'm trying to figure out what your point is. Is it a criticism of the article? Are you sharing with us that you are clever? I'm trying to give it a generous interpretation, but I'm having a hard time.
So it's not complicated to you... what made you want to share this?
Re: URLs: It's Complicated
#6It doesn’t seem complicated at all. Complicated to me means difficult to understand. This just involves reading the spec and it all seems pretty simple and consistent. Complicated doesn’t mean “new to me.” If I haven’t read a man page, that doesn’t mean the command is complicated.
> This just involves reading the spec and it all seems pretty simple and consistent.
Worth noting from the article:
> And this is one of the main take-aways here: while the URL specification prescribes or allows one thing, different clients and servers behave differently.
Re: URLs: It's Complicated
#7Specifically using another font for the code tag then the rest of the blog to hide the difference between ⁄⁄ and // seems weird. I get that it wouldn't be interesting if not doing that, but doesn't that just show that it's really not as complicated as you make it out to be?
Re: URLs: It's Complicated
#8It seems like the colon is too ambiguous (is used as a protocol delimiter, delimiter for user/pass, delimiter for port). Reminds a little bit of Java labels where you can do this: public class Labels { public static void main(String args[]){ https://hn.ycombinator.com for(int i=0; i the https: is a label named https and everything after the colon is a comment so this is valid code.
> It seems like the colon is too ambiguous (is used as a protocol delimiter, delimiter for user/pass, delimiter for port).
and because that was still too boring they came up with ipv6
Re: URLs: It's Complicated
#9It seems like the colon is too ambiguous (is used as a protocol delimiter, delimiter for user/pass, delimiter for port). Reminds a little bit of Java labels where you can do this: public class Labels { public static void main(String args[]){ https://hn.ycombinator.com for(int i=0; i the https: is a label named https and everything after the colon is a comment so this is valid code.
> It seems like the colon is too ambiguous (is used as a protocol delimiter, delimiter for user/pass, delimiter for port). and because that was still too boring they came up with ipv6
[deleted]
Re: URLs: It's Complicated
#10It doesn’t seem complicated at all. Complicated to me means difficult to understand. This just involves reading the spec and it all seems pretty simple and consistent. Complicated doesn’t mean “new to me.” If I haven’t read a man page, that doesn’t mean the command is complicated.
If we're being sticklers for reading the docs...
> com·pli·cat·ed | ˈkämpləˌkādəd |
> adjective
> 1 consisting of many interconnecting parts or elements