If you know the difference between em dash, en dash, and hyphen, you start seeing it everywhere—whether thet are used correctly or not. Books tend to have correct typesetting, so if you see a dash used as an em dash ought to be used, and if it looks kinda long, you can assume it's an em dash. AFAIK often manuscripts are submitted either with hyphens or --- in place of em dashes and then the editor or typesetter fixes it.
Also, it's called em dash because it's as long as the letter m (as a rule of thumb), so it's usually an easy visual comparison. Finally, a typeface with hyphens as long as em dashes would be terrible and quite noticeably wrong!
(To two-boxers) it's not half an analysis because once you walk into the room your choice is causally independent of the demon/AI/alien prediction.
There's something vaguely similar to the fallacy of proposed (Cooperate,Cooperate) solutions to the Prisoner's Dilemma. The arguments go as follows: (1) if we're both rational agents and we have the same information and same payoffs, we will make the same choice; (2) therefore, (Cooperate,Defect) and (Defect,Cooperate) are out of the question; (3) therefore, the only options are (Defect,Defect) and (Cooperate,Cooperate); (4) so I should Cooperate since it gives the better payoff. It seems to follow logically but (1) and (2) are problematic because you can't assume symmetrical solutions and thus eliminate asymmetrical outcomes, because that is essentially the same as saying "what I choose causally affects what my opponent chooses".
In the same way, one-boxing is irrational (for this argument, anyway; I'm undecided myself) because the prediction has already been made, and so your choice to one-box or two-box cannot have any causal relevance to the contents of the boxes. Even a perfect predictor cannot invert the flow of causality.
Units is a cool piece of software, but I have since switched to qalculate.
Mostly units has some silly defaults like needing to type tempC(30) instead of 30C; and it's nice to have a full calculator.
I know it's a way to specify that the conversion is absolute rather than relative, but qalculate just asks you about it the first time you convert, and since converting oven and outside temperatures is most of what I do, I don't havr to bother with remembering a different syntax.
Also qalculate is an awesome piece of software in general, so if you're excited by units you should check it out!
I have been using breezy weather and I like it overall. But after reading this article I can't help but be bugged off that the information density in the main page is significantly worse here than in Dark Sky.
Dark Sky showed hourly forecast with a 2h resolution. This is a negligible difference in precision IMHO (weather predictions are inherently imprecise anyway - and a more precise graph could be - is - one tap away), but it allows to show a time range that is twice as wide! On my screen, breezy weather is able to show me the forecast for the next 5h until I scroll - this is OK, but it's annoying. The hours are very spaced apart, and there is a 1h resolution. With tighter spacing and 2h resolution, 12 or 16 hours could be displayed at once - which is far more likely to cover the time I am going to spend outside, which as the article states, is the main reason why I might want to check an hourly forecast anyway.
All the other android apps mentioned here have the same issue.
I might try to open an issue in their GH, or even a PR... A toggle for "denser graphs" and a setting for hourly resolution could do wonders.
Although it wouldn't require a lot of work to allow side-loading apps on LineageOS and similar, LOS users would still be profoundly impacted by the death of the FOSS ecosystem.
LOS/AOSP/whatever users are a VANISHINGLY small minority of users, so "an app that only works on them" is an app that only works for a tiny minority of people. This would disincentivize developing FOSS apps altogether. A lot of projects will likely eventually die, and a lot that could have started will not.
Also, it's called em dash because it's as long as the letter m (as a rule of thumb), so it's usually an easy visual comparison. Finally, a typeface with hyphens as long as em dashes would be terrible and quite noticeably wrong!