Actually, it’s a a bit of a shitpost. Anything after the ‘?’ is an argument for the html request. Can and is used for tracking, but is also used for website functionality.
Sure, because it’s super fun to parse a path with multiple keypair that can be repeated, be non mandatory, etc. You must work for the GS1 project.
Developers are known to enjoy whipping themselves all the time, constantly trying to do obtuse things with the wrong tool when there’s a perfectly working, perfectly standard way of doing something that’s supported by literally every solutions under the sun.
Actually, it’s a a bit of a shitpost. Anything after the ‘?’ is an argument for the html request. Can and is used for tracking, but is also used for website functionality.
IMO, any developer who uses URL parameters for required functionality is short sighted. They should use the path as required parameters.
Sure, because it’s super fun to parse a path with multiple keypair that can be repeated, be non mandatory, etc. You must work for the GS1 project.
Developers are known to enjoy whipping themselves all the time, constantly trying to do obtuse things with the wrong tool when there’s a perfectly working, perfectly standard way of doing something that’s supported by literally every solutions under the sun.
/s, just in case.