Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
When coming to bits and bytes there should be a choice if the prefix kilo means 1000 (what it is right now) or if it should be kilo = 1024 (which I would prefer).
Any pros or cons on this one?
There's already "kibi" or "Ki", which is more accurate. "kilo" means 1000, "kibi" means 1024. Same for "mebi", "gibi", etc.
I don't think it's a good idea to mix these; it would just complicate Qalculate! and introduce an ambiguity that has historically messed up things since it's not always used. For example, a "200 GB" hard disk drive has 200,000,000,000 bytes, while a "1 GB" RAM has 1,073,741,824 bytes. And a "1.44 MB" floppy disk has 1.44*1000*1024 bytes.