Yes, same amount of bits, but different number of digits and thus screen real estate. I was speaking from personal experience. One of the reasons I made it eas

Yes, same amount of bits, but different number of digits and thus screen real estate. I was speaking from personal experience. One of the reasons I made it easy to toggle between F and C in my app was so I could adjust from F to C (in Korea). I think it worked and I am comfortable using both C and F now (although I admit I am more accustomed to F). However, one thing I noticed when I switch to C in my app is I get less information. I have seen systems that double the C reading to get a similar precision as F, but then it is no longer really C. My point was not that temperatures don't go over 100F, but that F uses the entire range of 2-digit readings. C only uses half of the positive 2-digit range. Also because freezing in F is above 0, you can show a useful range of temperatures below freezing before having to add a negative sign. So I still argue F is more information-dense than C given a 2-digit temperature reading for weather.