| 00:01:51 | | BearFortress joins |
| 00:22:41 | | Megame (Megame) joins |
| 00:22:41 | | Megame quits [Remote host closed the connection] |
| 00:41:31 | | etnguyen03 (etnguyen03) joins |
| 00:49:56 | | wyatt8740 quits [Ping timeout: 268 seconds] |
| 01:00:31 | | wyatt8740 joins |
| 01:20:38 | <systwi_> | TheTechRobo: https://mnbot.very-good-quality-co.de/item/0c1acb3a-9d41-4a72-908d-bc55937c0fa5 |
| 01:21:09 | <systwi_> | The tooltip says "_lower_ priorities are run first," shouldn't it be the reverse, or am I understanding it wrong? |
| 01:21:42 | <systwi_> | Oh wait, I think I'm looking at it wrong. |
| 01:21:49 | <systwi_> | -10 is certainly lower than 10. |
| 01:22:15 | <systwi_> | Higher priority from a lower number. |
| 01:24:36 | <pokechu22> | It would be better phrased as "lower values are ran first" rather than saying priority |
| 01:25:49 | <systwi_> | Or, to split hairs a bit, "lower values are run first," as ran is past-tense. |
| 01:25:55 | <systwi_> | But yes I agree. |
| 01:26:24 | <systwi_> | (nothing personal, just an OCD thing--you should see me trying to write an e-mail for work!) |
| 01:28:00 | <systwi_> | Takes me like half an hour to ensure it's just-perfectly-so. |
| 01:32:06 | <@JAA> | Agreed on 'lower values'. My entire argument in #jseater about using niceness is to avoid the ambiguity of 'priority' because some systems are 'higher values first' while others are 'lower values first'. Niceness shouldn't have that ambiguity (higher value = nicer to other tasks = letting them take precedence). But that goes out the window when you describe it as 'lower priority' again. :-D |
| 01:49:13 | <TheTechRobo> | Right, that part of the dashboard came before JAA suggested 'niceness' |