| 10:40 | <sffc> | Which VSCode ecmarkup extension should I use: "rbuckton.ecmarkup-vscode", 1421 downloads, by rbuckton, last updated 9 years ago, or "magicworks.ecmarkup", 150 downloads, last updated 7 months ago, by "Magic Works", who seems to publish a lot of language extensions |
| 10:42 | <ryzokuken> | I use the latter which is supposed to have a couple extra features |
| 10:42 | <ryzokuken> | and supports newer patterns that we use a lot |
| 10:44 | <ryzokuken> | oh magic works is Jack Works I believe |
| 11:02 | <Jack Works> | oh magic works is Jack Works I believe |
| 12:35 | <rbuckton> | Mine is fairly out of date and I haven't had much time to update it. |
| 12:37 | <ryzokuken> | akin to TCQ this could be perhaps benefit from some love from more committee members... |
| 15:12 | <snek> | stuff like this markup extension, tcq, esvu, etc... would be nice if we had them under shared ownership. no requirement from anyone in particular to maintain them, just some sort of way to keep things flowing as people and their availability come and go. |
| 15:29 | <bakkot> | ecmarkup lives under the tc39 org |
| 15:29 | <bakkot> | (and ecmarkdown, which is a distinct project for some reason) |
| 15:31 | <bakkot> | if you want to transfer esvu to the tc39 namespace I would be supportive! |
| 15:34 | <Chris de Almeida> | what's the difference between esvu and jsvu? |
| 15:36 | <nicolo-ribaudo> | Trademark opinions, clearly |
| 19:33 | <snek> | Chris de Almeida: jsvu has arbitrary rules for what engines they will accept. whereas esvu is more open to anything. |
| 19:34 | <snek> | although take that with a grain of salt, i haven't tried to add an engine to jsvu in many many years so maybe they're nicer about it now |
| 19:35 | <snek> | esvu is also used for test262 infra though, so its somewhat within the scope of things tc39 could theoretically be responsible for. |