this post was submitted on 25 May 2024
68 points (73.0% liked)

Mildly Infuriating

35435 readers
1332 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 1 year ago
MODERATORS
 
all 25 comments
sorted by: hot top controversial new old
[–] [email protected] 61 points 5 months ago (1 children)

Here is what I get when I complete the search.

And here’s what I get when I intentionally change the units. Notice the color difference?

[–] [email protected] 9 points 5 months ago (2 children)

I don't think that's the issue, OP also changed from 1 to 2, so I believe they basically want to know the result of 2 * 1024 * 1024, but the issue is that the result is written in scientific notation.

[–] [email protected] 17 points 5 months ago (1 children)

When you search “megabytes to bytes” the units are correct and the number is one. If you edit the form, the number might not be one and the units might not be correct. Changing units highlights the unit input.

OP’s ostensible point posting on this community is that searching “megabytes to bytes” gave “mebibytes to bytes” in the calculator but OP’s image shows OP has changed the calculator.

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago) (2 children)

I don't see any reply from OP so I'm growing confident that what you're talking about is not OP's point.

Often times when coding you may want to quickly write down 2MB but you may need to type it in bytes, so either you calculate 2 * 1024 * 1024 while coding, or you remember the number 2097152.

Now, since 2097152 is not such a common number that one would remember, you may quickly turn to the globally acclaimed ~~oracle~~ search engine to get such an answer, but all you get is a number in scientific notation, approximated, without an option to read it in standard decimal base. So you have to open the calculator and ask the same question again to get the answer you need.

If it helps, try to ignore what's in the search bar and tell me if it makes more sense.

Edit: Additionally, if you were to NOT use the scientific notation, the length of the result would be shorter:

2,097e+6 (8 characters) vs 2097152 (7 characters)

[–] [email protected] 9 points 5 months ago* (last edited 5 months ago)

Yeah. This was the problem. i just wanted to copy and paste it quickly but they rounded it off. It's a useless conversion. And I switched it to mebibytes as well since that's what everyone really means when they say megabytes unless you're ~~making~~ selling storage devices. =]

Indeed, I should have just used my calculator program.

[–] [email protected] 4 points 5 months ago (1 children)

If I ignore what’s in the search bar, I remember that the prefix “mebi” means 2^20 and use a calculator. Your point doesn’t make sense because you’re asking us to get mad at a tool intended to convert scientific units for using the bog standard scientific notation. Byte math uses powers of 2 ergo we should use a calculator that isn’t explicitly set up for rounding.

[–] [email protected] -3 points 5 months ago (1 children)

Are you telling me that whenever you work with Digital Storage units you should never use scientific notation?

[–] [email protected] 3 points 5 months ago (1 children)

You literally spent an entire comment explaining why you should not use scientific notation and now you’re asking why I might prefer precision in byte arithmetic?

Good luck with that.

[–] [email protected] -3 points 5 months ago* (last edited 5 months ago)

Nope, au contraire, I agree, I'm just pointing out that you said that digital storage conversion should happen in non-scientific notation, so you should now agree with OP in that Google is choosing the wrong output format for a, quote from the screenshot, "Digital Storage" conversion.

And yes, I'm writing multiple comments trying to explain this through narrative, without having to point out what in your reasoning sounds stupid.

I.E. Now don't you tell me that Google is incapable of figuring out which output format it should use for such a calculation...

Since I apparently need to explain this like you're 5, please read my last comment like the following:

"Are you now agreeing with me/OP that whenever you work with Digital Storage units you should never use scientific notation?"

[–] [email protected] 13 points 5 months ago (1 children)

What's wrong? I find this a reasonable result. Most people looking for megabyte to bytes are actually looking for mebibytes, since the mega- prefix is literally just times a million but a lot of programs actually list mebibytes as "megabytes".

[–] [email protected] 5 points 5 months ago

Sorry, I changed it manually. I should have cropped out the search.

[–] [email protected] 7 points 5 months ago (2 children)

?? It's correct, what's the issue here?

[–] [email protected] 7 points 5 months ago (1 children)

Maybe the OP can't read scientific notation?

[–] [email protected] 1 points 5 months ago

Sounds like a skill issue

[–] [email protected] 5 points 5 months ago (1 children)

It does not give the exact answer, only an approximation.

[–] [email protected] 3 points 5 months ago

Ah OK, good point. I tend to forget that 'good enough' is not what other people might want in their measurements precision

[–] [email protected] 7 points 5 months ago (1 children)

GPT gave me this yesterday:

To convert 500 KiB/s to a more common unit like megabits per second (Mbps):

  1. Understand the conversion factors:

    • 1 KiB (Kibibyte) = 1024 bytes
    • 1 byte = 8 bits
  2. Calculate the speed in bits per second:

    • 500 KiB/s = 500 * 1024 bytes/s = 512000 bytes/s
    • 512000 bytes/s * 8 bits/byte = 4096000 bits/s
  3. Convert bits per second to megabits per second:

    • 1 Mbps = 1,000,000 bits/s (for simplicity, although technically 1 Mbps = 1,048,576 bits/s, the simpler metric is usually used for network speeds)
    • 4096000 bits/s / 1,000,000 = 4.096 Mbps

So, 500 KiB/s is approximately 4.1 Mbps.

I was like, I just wanted the answer!

[–] [email protected] 7 points 5 months ago

That's for its own benefit. It has to talk through it (or alternatively code through it) to work out the answer. S'just showing its work.