Why does the order matter? Wouldn't it be easier to keep it the same?
Ask HN: Queryparams have a starting? and then and as seperator..why?
1–4 of 4 posts
Re: Ask HN: Queryparams have a starting? and then and as seperator..why?
#2I think & is a valid character for path names. You probably need the ? to know the query has begun.
Re: Ask HN: Queryparams have a starting? and then and as seperator..why?
#3> It was Marc Andreessen who suggested our current method based on what he had already implemented in Mosaic...
https://eager.io/blog/the-history-of-the-url-path-fragment-q...
Re: Ask HN: Queryparams have a starting? and then and as seperator..why?
#4> It was Marc Andreessen who suggested our current method based on what he had already implemented in Mosaic... https://eager.io/blog/the-history-of-the-url-path-fragment-q...
> You may have also noticed that cookies follow a similar, but different format: x=1;y=2 which doesn’t actually conflict with HTML character encoding at all. This idea was not lost on the W3C, who encouraged implementers to support ; as well as & in query parameters as early as 1995.
I wish the w3c had won that one.