Technology

60080 readers

3368 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

Why a kilobyte is 1000 and not 1024 bytes (zeta.one)

submitted 1 year ago by [email protected] to c/[email protected]

168 comments fedilink hide all child comments

I often find myself explaining the same things in real life and online, so I recently started writing technical blog posts.

This one is about why it was a mistake to call 1024 bytes a kilobyte. It's about a 20min read so thank you very much in advance if you find the time to read it.

Feedback is very much welcome. Thank you.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] -4 points 1 year ago (1 children)

I tried to make the title the exact opposite of clickbait. There are no unanswered questions on purpose. No "Find out if a kilobyte is 1024 bytes or 1000 bytes". I think people are smart enough that I not just reiterate for 20min why a kilobyte is 1000 bytes but instead go into more details.

The main problem is probably that people won't sacrifice 20min of there time on something they are not sure if it's a good read but the only thing I can do is trying to encourage them to read it anyway.

There are not ads, no tracking, no cookies, no login, no newsletter, no paywall. I don't benefit if you read it. I'd like to clear up misconceptions but I can't force people to read it.

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

I don’t benefit if you read it.

You don't benefit financially, but there are other benefits. For example, you specifically asked for feedback, and you have received some.

[+] [email protected] -7 points 1 year ago (1 children)

I don't get feedback just because you read it. I'm thankful for feedback but my sentence was accurate. I don't benefit if you read it.

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

Every part of your comment has something factually wrong or fallacious.

I don’t get feedback just because you read it.

My reading the part I am giving feedback on is a prerequisite for actually giving feedback. I am obviously a person who graciously responded to your request, not somebody that you somehow ordered to give feedback. I don't know what you think you gain from viewing it this way.

I’m thankful for feedback but my sentence was accurate.

I didn't say it was inaccurate, but that it didn't tell people why to read the article. You didn't ask me to tell you inaccuracies. You asked for "feedback". You also don't seem to be thankful, because if you were thankful, you'd simply accept the feedback instead of throwing up straw-man arguments.

I don’t benefit if you read it.

You have exactly repeated your previous statement that I already proved wrong.

I will offer you one last piece of feedback. Just stop arguing. You can never look gracious pursuing an argument where you ask for advice and then argue with people who took time out of their day to help you.

Upvotes and downvotes don't determine whether people are factually right, but they do help you gauge what people think when they read your comments, and what I'm seeing is that you're not ingratiating yourself to the people who you are asking to read your article. Even if you could win this argument, and you can't, you wouldn't want to, because you'd look bad in doing so. When you ask for feedback, and feedback is given, just graciously accept it. If it's bad feedback, then just ignore it.