| 14:31 | <jschoi> | Are there definite guidelines or criteria for when a proposal issue is “finished”—when we should close the issue? Sometimes an issue asks for a concrete actionable change, and, if the change is added to the repository, then the issue is clearly “finished” and should be closed. But oftentimes the issue doesn’t yield an actionable change, and it becomes a long discussion that goes in circles and repeats the same arguments. This can go on for years. If there’s nothing really actionable in the issue, but discussion is still occurring, then when is the issue “finished”? When is it appropriate to close it? (Background: https://github.com/tc39/proposal-pipeline-operator/pull/214#discussion_r709774469) |
| 14:55 | <ptomato> | really depends on the situation. I closed a lot of open discussion-type issues when Temporal reached stage 3 with a message like, "we acknowledge that X has the advantages of Y and Z, but the decision that we decided to move forward with is A because B and C weighed more strongly." but these probably involved orders of magnitude less strong feelings than pipeline |
| 15:02 | <ptomato> | I agree that it should be OK to close things even if discussions are still going on, if they aren't getting anywhere. although sometimes you get a little more goodwill by just letting the discussion burn itself out, then closing the issue |
| 15:02 | <ptomato> | Shane did some good work of that type in this thread: https://github.com/tc39/proposal-temporal/issues/1454 |
| 21:23 | <rkirsling> | on a keyboard with combining ^, wouldn't ^) or ^, still be typable without an extra keystroke? |
| 21:23 | <rkirsling> | ^ leobalter, I suppose |
| 21:25 | <leobalter> | rkirsling: If I'm writing ^( I really never type Shift+6 and ( |
| 21:25 | <leobalter> | but Shift+6, space, and Shift+9 (() |
| 21:25 | <rkirsling> | interesting |
| 21:25 | <rkirsling> | that's a matter of habit though? |
| 21:26 | <rkirsling> | (I'm not arguing for ^ here, I'm just genuinely interested) |
| 21:26 | <leobalter> | same thing for string quote characters, including back quote |
| 21:26 | <leobalter> | mechanical habit, yes |
| 21:26 | <leobalter> | because some of these are also applied in conjunction to other letters |
| 21:27 | <leobalter> | in pt-BR we only mix ^ with aeo, but it might also fall into other letters, no limited to vowels, I guess |
| 21:27 | <leobalter> | it's even for quotes |
| 21:28 | <leobalter> | like ' for áéíóúç |
| 21:29 | <leobalter> | the keyboard capabilities go beyond what my language grammar allows, so without a space key press, it's a guess game |
| 21:41 | <leobalter> | rkirsling: https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-921274859 |
| 21:44 | <rkirsling> | like |
| 21:45 | <rkirsling> | oh wait |
| 21:45 | <rkirsling> | you just demonstrated that you get a different thing from ^ |
| 21:45 | <rkirsling> | that's shocking |
| 21:45 | <rkirsling> | what a bummer |
| 21:46 | <leobalter> | for ^), ^, the spacebar keystroke in between is required |
| 21:47 | <rkirsling> | that is super unfortunate behavior |
| 21:47 | <rkirsling> | but I appreciate the knowledge |
| 21:49 | <leobalter> | TIL option+i is equivalent to Shift+6 |
| 21:58 | <rkirsling> | ah. that one works for the US keyboard too |
| 21:58 | <rkirsling> | and does indeed demonstrate the issue you mentioned |
| 21:58 | <rkirsling> | so I guess I was just being naive |
| 22:06 | <jschoi> | TIL option+i is equivalent to Shift+6 |
| 22:07 | <jschoi> | Typing ⌥I then Space leaves ˆ, not ^. |
| 22:07 | <jschoi> | But in keyboard layouts with dead-key modes, typing ⇧6 then Space inserts ^, right? |
| 22:18 | <jschoi> | I think we should generally optimize for ease-of-reading over ease-of-typing. But in this case the trade-offs either way are somewhat small (it depends on how frequent remainder % occurs over bitwise xor ^, and typing Space-then-Backspace every time after typing ` or ^ or whatever is not catastrophic but is also annoying). |
| 22:19 | <ljharb> | how do international elixir users handle this, since they use ^ for their pattern matching pin operator? |
| 22:40 | <leobalter> | ljharb: I know the guy who created Elixir, who is also a brazilian. lol, I guess Valim picked the ease-of-reading side |
| 22:41 | <leobalter> | in my case is just bias, the convenience of typing is higher than the visual benefits if I compare % and ^. There isn't much else for me to argument on this |