| 10:38 | <Igor «InoY» Zviagintsev> | Hi everyone! I don't sure it is a right place for that but I don't know another place for. Today I found functions parseInt and parseFloat is not locale aware. I mean a code parseFloat('1.2') with dot as decimal separator (North America style) returns 1.2 but parseFloat('1,2') (Eastern Europe style) return 1. Also parseInt('1_000_000') return 1 but the string 1_000_000 is correct string for numbers since ES6 (ES7?) |
| 11:12 | <bakkot> | Igor «InoY» Zviagintsev: yup, that is an accurate observation |
| 11:13 | <bakkot> | it's not going to change though - many people rely on the behavior of parseInt being what it is |
| 11:15 | <bakkot> | and localized parsing is extremely fraught; see e.g. https://blog.sffc.xyz/post/190943794505/why-you-should-not-parse-localized-strings |
| 11:15 | <bakkot> | see also https://github.com/tc39/ecma402/issues/1 and the several linked issues |
| 12:37 | <jmdyck> | urgh. Is there some way to disable threads in the element web app? |
| 12:37 | <bakkot> | not afaik |
| 12:41 | <eemeli> | No. |
| 13:12 | <Chris de Almeida> | there is a client, I forget which, that has the threads in the main chat, but I don't recall which or how it works |
| 13:36 | <littledan> | I'm fine with threads, I just want to clear all the "unread" stuff |
| 14:11 | <shu> | i hate the threading in element too |
| 14:11 | <shu> | anything in a thread is "im happy for you tho, or sorry that it happened" for me |
| 17:45 | <Chris de Almeida> | https://cinny.in/ |
| 17:46 | <Chris de Almeida> | Cinny is the client that displays threads inline, in the same way as if they were just regular replies |
| 17:47 | <Chris de Almeida> | example ☝️ |
| 17:54 | <Andreu Botella> | I'm pretty sure older versions of Element also do that |
| 17:55 | <Andreu Botella> | I think thread messages are represented as replies to the previous message in the thread with extra metadata |