Re: [whatwg/url] Support relative URLs (#531)

> I think we could solve that with a simple data structure containing the broken-down URL components -- e.g. a list of path segments you could directly append to/remove from, and some simple methods to define how we serialise that structure as a relative reference.

URLs are that simple datastructure that contain the broken down components. And this is about coming up with an API for that.

> I think it's important to remember that the URL parser in this standard does not represent the cleanest definition of URLs.

I know the standard well enough to say that the hacks _can_ be described in a clean way. The differencess with RFC3987 are painfully small.

> For new APIs which don't have any of those compatibility concerns, I think we should be striving for the simplest design that solves the problems we actually have. 

And I was hoping to come up with a very simple API.

> But instead, you're just coming and saying you've solved all the problems on your own, in a purely academic exercise that has not been used in production and is apparently not even driven by specific problems encountered in a real application (or was it?).

I reject that story line. I was pushed into this position and had no other choice than to respond. Yes, I have written implementations. And do not dismiss academic exercise as useless.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/531#issuecomment-1033192682
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/531/1033192682@github.com>