undefined
@bagder @suzannealdrich @jbqueru
If Curl and Firefox start by advocating "this is the spec for URIs, and other things might work or might not" that would already be a good start for the free internet.
Then we only have Chromium to convince, and the rest follows implicitly.
@bagder @suzannealdrich @jbqueru
Taking a stab in the dark with some EBNF:
url ::= protocol '://' [ name [ ':' name ] '@' ] [ server ] [ '/' [ path ] [ '?' arg { '&' arg } ] ]
protocol ::= name
server ::= name { '.' name }
path ::= name { '/' name }
arg ::= name [ '=' name ]
name = ([^:/@?&=.%]|%[0-9a-f][0-9a-f])+
I understand that whatwg makes that :// not a required part ... but this kinda matches what my naive brain thinks of as a URL and how to read it.
@bagder @suzannealdrich @jbqueru
I know I'm coming at URL parsing from a clean brain, but can't we specify the base things in an actually parseable way? Surely it's not *that* hard to parse a URL?
@vitaut It's called C++29 so German companies can tell people whether they can use C++20 yet: C++20? Nein!