@feeks01: Just like meters and feet are both units of measurement. Doesn't mean they're the same thing.
@dmitriar: What convention would that be?
@stefanpe: Instead of complaining that this is not a bug, you could have pointed me to the right place to post a... feature request... improvement? I will be less likely to report bugs in the future, as well as refrain from using a piece of software with such a hostile developer base. And yes, I do believe the confusion of bits and bytes warrants a bug report on a defragmentation software's website.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@oKtosiTe:
I didn't complain, I just asked two simple questions, since the single sentence and a link to a page isn't enough for me.
I wanted to know your opinion, not the one of Wikipedia.
The tracker can always be changed from "Bugs" to "Feature Requests", so there is no need to create a new entry.
Wikipedia is not fully complete and content is added by many individuals, so a book on computer science would be better qualified to base such a problem report on.
Just my personal opinion ;-)
We will see what we can do about this, but it needs further collecting of information.
--
Stefan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I ended up here because I saw a screenshot of UltraDefrag on PortableApps.com and it immediately jumped out at me. I wouldn't use a defragmenter that confuses bits with bytes, because in my personal opinion, it looks unprofessional and unpolished.
While I agree that Wikipedia is not a definitive resource, I find it is often indicative of opinion and consensus at large.
Last edit: Anonymous 2014-11-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have checked the code and we are currently checking for the size suffix ignoring the case, so changing the handbook and the usage pages of the executables wouldn't break anything.
You can already use GB, gB, Gb or gb for gigabytes without the program ending up to malfunction.
I have changed this to a feature request now, hope you don't mind ;-)
--
Stefan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Stefan: Thank you, and my apologies for getting a bit annoyed before. It's good to know "bug" reports don't fall on deaf ears here, and I look forward to giving your defragmenter a go in the near future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Why is this a bug?
Is the program working incorrectly due to this?
--
Stefan
I believe this isn't a bug, we're just using the old-style convention.
I looked at the reference from the original email and it described both GB and Gb with the same phrase
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
@feeks01: Just like meters and feet are both units of measurement. Doesn't mean they're the same thing.
@dmitriar: What convention would that be?
@stefanpe: Instead of complaining that this is not a bug, you could have pointed me to the right place to post a... feature request... improvement? I will be less likely to report bugs in the future, as well as refrain from using a piece of software with such a hostile developer base. And yes, I do believe the confusion of bits and bytes warrants a bug report on a defragmentation software's website.
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
From the linked Wikipedia article on gigabytes:
The unit symbol for the gigabyte is GB or Gbyte, but not Gb (lower case b) which is typically used for the gigabit.
@oKtosiTe:
I didn't complain, I just asked two simple questions, since the single sentence and a link to a page isn't enough for me.
I wanted to know your opinion, not the one of Wikipedia.
The tracker can always be changed from "Bugs" to "Feature Requests", so there is no need to create a new entry.
Wikipedia is not fully complete and content is added by many individuals, so a book on computer science would be better qualified to base such a problem report on.
Just my personal opinion ;-)
We will see what we can do about this, but it needs further collecting of information.
--
Stefan
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
Well, I ended up here because I saw a screenshot of UltraDefrag on PortableApps.com and it immediately jumped out at me. I wouldn't use a defragmenter that confuses bits with bytes, because in my personal opinion, it looks unprofessional and unpolished.
While I agree that Wikipedia is not a definitive resource, I find it is often indicative of opinion and consensus at large.
Last edit: Anonymous 2014-11-28
I have checked the code and we are currently checking for the size suffix ignoring the case, so changing the handbook and the usage pages of the executables wouldn't break anything.
You can already use GB, gB, Gb or gb for gigabytes without the program ending up to malfunction.
I have changed this to a feature request now, hope you don't mind ;-)
--
Stefan
Another source http://kb.iu.edu/data/ackw.html includes a warning to not confuse GB with Gb, which is GigaByte versus GigaBit.
So we will change that.
--
Stefan
According to http://en.wikipedia.org/wiki/IEEE_1541-2002 we should even use GiB, but that would confuse people only.
So we use more or less the http://en.wikipedia.org/wiki/SI_units prefix instead of the http://en.wikipedia.org/wiki/Binary_prefix
For consistency with the other units we use a capital K for kilo instead of the lower case k defined by the SI standard.
--
Stefan
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
@Stefan: Thank you, and my apologies for getting a bit annoyed before. It's good to know "bug" reports don't fall on deaf ears here, and I look forward to giving your defragmenter a go in the near future.
Fixed in v5.0.7
--
Stefan