Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

file size column in bytes after version 4.57?

2011-07-15
2013-08-10
  • Mister Spoon
    Mister Spoon
    2011-07-15

    Was wondering why this happened and can't seem to find an option to change it back.  Really don't see the sense in having a file that says 1 000 000 instead of 1000 MB like this older version…

    Did a search, found one person asking the same thing with no response.  Didn't feel like going through the rest of the 25 pages of results. 

    size column

     
  • Igor Pavlov
    Igor Pavlov
    2011-07-15

    The problem with 1.2KB / 1.2MB / 1.2 GB things, that you need time to recognize these G / K / M letters. So you can't estimate size of file as fast as with long string like 1 200 000. So when you look long-scheme sizes, you can estimate sizes for all files on screen. For short-scheme sizes you can estimate the size only for one file at time.

     
  • Mister Spoon
    Mister Spoon
    2011-07-15

    Thanks for the quick reply.

    It would slow it down that much?  I would assume with computers being as powerful as they are today that that calculation would only take nanoseconds. 

    Version 4.57 seems to work fine or me. So guess I'll continue to use it :)

     
  • Igor Pavlov
    Igor Pavlov
    2011-07-16

    No, humans are slow for complex recognition.

    If you see 2 long lists:
    1)
    12 KB
    55
    23 MB
    7 GB
    ….

    or

    2)
    12 000
    55
    23 000 000
    7 000 000 000

    in second list you can find all big files faster.

     
  • AeSix
    AeSix
    2013-08-07

    You're kidding, right?
    I can understand setting that as default behavior, but removing the option completely is pretty damned socialistic of you Igor.
    You do know there are some of us out here in the rest of the world that can differentiate between M G B K and so on, right? It takes more fucking effort for a human to turn long strings into something manageable than it is to look at a letter, read it and know what it stands for.

    And Thank You, Thank you Very much for telling me I'm too fucking stupid to know the difference and that I'm too stupid to even have the option to be able to read file sizes in the format I want. I hope the rest of your users appreciate being told how stupid they are as well.

    Because that is all you've done here. You've taken away a tool from us, and justified it by saying we're too stupid to use it.

    Grow the fuck up Igor, and stop dictating what your users can and cannot do, especially when it's something that the rest of the fucking world already allows.

    With the posting of this, I am moving on to removing 7zip from every system I have, and letting everyone I know that they should probably consider doing the same.

    I'm just ashamed it's taken me this long to realize this whole issue. And I'm ashamed I've recommended 7zip to so many people. Fucking bullshit, Igor, FUCKING BULL SHIT!

     
  • dos386
    dos386
    2013-08-08

    "AeSex" wrote:

    And I'm ashamed I've recommended 7zip to so many people.
    Fucking bullshit, Igor, FUCKING BULL SHIT!

    Kill yourself, moron AeSex.

    You do know there are some of us out here in the rest of the
    world that can differentiate between M G B K and so on, right?

    What is M G B K ???

    Igor wrote:

    No, humans are slow for complex recognition.
    If you see 2 long lists

    Good point.

    Space for improvements:

    • use apo's instead of spaces ( 18'446'744'073'709'551'615 )
    • make an option (non-default) to use BUOB (KiB MiB GiB TiB PiB EiB ...)
     
    Last edit: dos386 2013-08-08
  • Shell
    Shell
    2013-08-08

    AeSix wrote:

    You're kidding, right?

    That was just a point of view. Some people like "short" numbers, some prefer "long" ones. Anyway, there is no good in insulting the author of a program that you use for free. It is a good point to add a feature request... or download the source code and fix the numbers for oneself.

    dos386 wrote:

    use apo's instead of spaces

    I think it would be more universal to consult operating system's regional settings for the right symbol (at least on Windows).

    make an option (non-default) to use BUOB

    Agree. Indeed, some people are more used to the "short" notation. However, it has one more disadvantage - a need for floating point. So it will be difficult to show kilo-, mega- and other-bytes on something like AVR8 :-)

     
  • dos386
    dos386
    2013-08-10

    it has one more disadvantage - a need for floating point

    NO. Feel free to pirate my code http://freebasic.net/forum/viewtopic.php?t=12600 if you can't do it without floats ;-)

     
    • Shell
      Shell
      2013-08-10

      Yes, dos386, I see now. I did not think of fixed-point arithmetic which suits the case perfectly.