Linked by Howard Fosdick on Fri 16th Nov 2012 07:43 UTC
Permalink for comment 542734
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2005-06-29
When I buy a computer with, say, a 500GB drive, I fully expect to see something more like 465GB due to GB/GiB shenanigans. On top of that, I know that the Microsoft OS du jour will take anywhere from 15-20GB by itself, and the restore partition (hidden or not) will take up another 10-20GB. At the worst extreme, that leaves me with 415GB when I paid for 500GB. That's 85GB of "missing" space, which as early as five years ago was a realistic size for an entire system drive.
That said, when you're dealing with disk sizes around 32GB and the mobile OS has an installed size of 16GB, there is indeed a problem. I think Microsoft should have advertised these devices based on the free space, and used a minimum of 64GB in the base model to avoid confusion and lost sales.