Agree. For things like semantic versioning, in which “1.20.1” and “1.2.1” are two different things, you want to pronounce them “one point twenty point one” and “one point two point one”, respectively. But that is a bit of an outlier. File size should be pronounced “normally”, because “1.20” and “1.2” are the same value.
I disagree. I would personally find one point two zero point one to be more natural and easier to understand.
I disagree with that, because we’re dealing with a number and not a fraction. Linux kernel 4.20 is not equal to Linux kernel 4.2, we’re actually dealing with the integer 20 here. (yes, alphabetical sorting on a download server has lead me to download an outdated kernel version once)
One point three two. To me, thirty two is an integer.
The only way you could use ‘thirty two’ correctly for that number would be ‘one and thirty two hundredths’ which would be pretty unusual.
Agree. For things like semantic versioning, in which “1.20.1” and “1.2.1” are two different things, you want to pronounce them “one point twenty point one” and “one point two point one”, respectively. But that is a bit of an outlier. File size should be pronounced “normally”, because “1.20” and “1.2” are the same value.
I disagree. I would personally find one point two zero point one to be more natural and easier to understand.
I disagree with that, because we’re dealing with a number and not a fraction. Linux kernel 4.20 is not equal to Linux kernel 4.2, we’re actually dealing with the integer 20 here. (yes, alphabetical sorting on a download server has lead me to download an outdated kernel version once)
Don’t you know that my head canon is universal canon? /s
You make a compelling point. I concede to your logic, but refuse to change my ways.