Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bits and Bytes all treated as bits #56

Open
0x85C opened this issue Jul 1, 2020 · 1 comment
Open

Bits and Bytes all treated as bits #56

0x85C opened this issue Jul 1, 2020 · 1 comment
Labels
core For issues related to core Rink functionality enhancement

Comments

@0x85C
Copy link

0x85C commented Jul 1, 2020

Hi,

There is some odd behavior between bits and bytes, (i.e. GB, Gb, GiB) all being treated as the same unit and converted to bit, where the 3 units are distinctively different units.

Example:
"5 bytes" becomes "40 bit"
"800GB" becomes "6.4 terrabit"

Also as a side note "TB" is recognized as a terrabyte/bit, however "Tb" comes up as a tablespoon. Maybe tablespoon can be changed to "tb" so that "TB" can be consistently used, similarly to gigabytes in the following different units (TB, Tb, TiB).

@tiffany352 tiffany352 added core For issues related to core Rink functionality enhancement labels Aug 7, 2020
@passcod
Copy link

passcod commented Jan 24, 2023

Ran into that today.

In general it would be nice if the units would stay within their "cohort" unless I ask for conversion or op with other units. Like

38 kilobytes * 100 * 365
= 1.4235 gigabyte

400 pounds * 1.5
= 600 pound

instead of

38 kilobytes * 100 * 365
= 11.096 gigabit

400 pounds * 1.5
= 272.1554 kilogram

tiffany352 added a commit that referenced this issue May 11, 2024
This has been annoying me for years. Make rink output bytes by default,
even though bits are the base unit of information.

Only applies when you specifically ask for bytes by itself. Falls back
to bits if you use some other unit like `bit s^-1`, `bit^2`, `bit^-1`,
etc.

```
> 500 floppy
737.28 megabyte (information)
```

Improves #56 but doesn't really fix it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core For issues related to core Rink functionality enhancement
Projects
None yet
Development

No branches or pull requests

3 participants