4 ms·
I wonder if he considered that even under a domain/host/path format, an autocomplete could probably be designed to ignore the domain and search the host. Eg, i
by SkyMarshal 6y ago
I wonder if he considered that even under a domain/host/path format, an autocomplete could probably be designed to ignore the domain and search the host.
Eg, if you're searching for com/welcometothejungle/en/collections/behindthecode, just start typing "welcometothejungle" and autocomplete will find that substring and return the full URL.
- waheoo 6y agoSolution in search of a problem. Whats the issue with having the domain name, an essentially flat map from name to number, going from least general to most general, and a path, representing a file system tree, going from most general down its nodes to the most specific? Is the argument they make up two parts of a url, and thus should behave the same way? Seems a bit superficial.
- SkyMarshal 6y agoYeah if your objective is differentiate between domain and file system path then that’s one way of doing it. That might help with parse-ability, especially if your protocol allows for an optional subdomain which may or not be there, so having a clear separation b/t domain and path might be useful. Hard to know without having been there when these decisions were being made.