| 00:14 | <andreubotella> | Bakkot: I suspect it's part of https://url.spec.whatwg.org/#concept-domain-to-ascii |
| 00:15 | <Bakkot> | neat, thanks andreubotella |
| 01:57 | <Krinkle> | Bakkot: it would appear that opening that url in Firefox, also shows the address bar normalising to https://a.com which suggests it is not limited to fetch() itself. |
| 01:58 | <Bakkot> | Krinkle: yeah, sorry, was asking about domain name normalization in general |
| 02:03 | <MikeSmith> | I know myself from experience that starting with a specific information need like that, it can often be pretty hard to figure out which spec defines it, and which specific part of that spec |
| 02:04 | <MikeSmith> | the style in which the specs are written doesn’t make it very easy |
| 02:05 | <MikeSmith> | not that I’m complaining; I actually like the way the Fetch and URL and Encoding specs are written, compared to how most other specs are written, or even compared to how the HTML spec is written |
| 02:08 | <MikeSmith> | but I think some cases, even an implementor who wrote browser code based on the specs would not be able to tell you which spec some part is defined in, and which specific part of that spec |
| 02:10 | <MikeSmith> | I mean, they would not be able to tell you afterwards, some time later after they had gone through writing the code, and needing to look back |
| 03:52 | <MikeSmith> | https://github.com/tabatkins/bikeshed/issues/1138#issuecomment-597959694 🎉 |
| 14:04 | <annevk> | hurray, everyone is wasting a lot of time on meaningless upstream changes from Python |
| 14:14 | <MikeSmith> | yeah, and more to come |
| 14:14 | <MikeSmith> | not sure what the alternative is, as far as dealing with what’s been handed to us |
| 14:57 | <Domenic> | Use Node.js instead! |
| 15:17 | <jgraham> | The node ecosystem is famous for never breaking anything! |
| 15:18 | <jgraham> | But, yeah the terrible disregard for backward compatibility in Python is distressing |
| 15:32 | <Domenic> | When Node core breaks things it's almost always by mistake. And third-party packages are pretty good about using semver. But the recent culture of reporting "security vulnerabilities" because you used a regex with backtracking or an object instead of a Map is causing a lot of upgrade churn, I admit. |