[01:06:01] It was a long time ago but I told @99of9 that there was little chance of Date changes in JS soon, there is actually a proposal on stage 3/4 of being implemented in the official spec that would make changes, which means there may be changes within a few years [01:09:18] This proposal supports dates of infinite range [01:12:44] Interesting, thanks for sharing. Where could one see this proposal? [01:12:57] GitHub [01:13:01] I'll find the link [01:13:22] GitHub - tc39/proposal-temporal: Provides standard objects and functions for working with dates and times. [01:13:22] https://github.com/tc39/proposal-temporal [02:18:18] This is a good example of where a few years down the track we may want to change the structure of one of our types (in this case just the JS code converters), and I fear it will be quite a difficult process. Would there be a way to support old implementations with old converters, and new implementations with the new ones??? (re @Feeglgeef: This proposal supports dates [02:18:18] of infinite range) [02:19:46] Yeah, this will end up being a big change as this is a whole new type, anything that depends on the Date object (which Temporal is not backwards-compatible to) will break if you make the switch (re @u99of9: This is a good example of where a few years down the track we may want to change the structure of one of our types (in this case...) [04:10:59] I wonder if this space should be used for "related functions" : https://tools-static.wmflabs.org/bridgebot/8b5267f7/file_68564.jpg [04:11:25] That would be nice (re @u99of9: I wonder if this space should be used for "related functions") [04:12:21] But mobile phones have to be considered, that would add a lot more scrolling to the already pretty significant amount to actually use the function or interact with it [04:12:42] Yes, I'd propose to put it at the bottom for mobiles. (re @Feeglgeef: But mobile phones have to be considered, that would add a lot more scrolling to the already pretty significant amount to actuall...) [09:23:01] The interface seems to change up quite often recently? But right now it looks a bit glitchy at Z19601 : https://tools-static.wmflabs.org/bridgebot/7b8d80d6/file_68569.jpg [09:35:30] [[Wikifunctions:Project chat#New Codex table]] You could always find a slightly longer name for the time being 🤷‍♂️ (re @u99of9: The interface seems to change up quite often recently? But right now it looks a bit glitchy at Z19601) [09:59:33] thank you @u99of9 and Al for the report! sharing this internally for further investigation [10:02:03] I can't see the problem there anymore. You might need to revert my recent edits at that page. (re @internetam1n: thank you @u99of9 and Al for the report! sharing this internally for further investigation) [16:05:11] This is polyfillable, which means that technically it can be implemented now in a type converter (re @Feeglgeef: GitHub - tc39/proposal-temporal: Provides standard objects and functions for working with dates and times. [16:05:12] https://github.com/tc...) [16:05:28] @vrandecic if you'd like to have a look at that [16:05:54] It's stage 3 so is likely to be implemented the same way when it becomes natively supported