• 0 Posts
  • 78 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle
















  • You asked for feedback, so here is my feedback:

    The article is okay. I read most of it, but not all of it, because it seemed overly worded for the sentiment. It could have been condensed quite a bit. I would argue the focus should be more on the fact that there should be a standard in technical documentation, OS’s, specification sheets, etc. That’s the part that impacts most people, and the reason they should care. But that kind of gets lost in all the text.

    Your replies here come off as pretty condescending. You should anticipate most people not reading the article before commenting. Just pay them no attention, or reiterate what you already stated in the article. You shouldn’t just say “did you read the article” and then “it’s in this section of the article”. Just like how people comment on youtube before watching the video, people will comment on the topic without reading the article.

    Maybe they didn’t realize it was an article, maybe they knew it was an article and chose not to read it, or maybe they read it and disagree with some of the things you said. It’s okay for people to disagree with something you said, even if you sincerely believe something you said isn’t a matter of opinion (even though it probably is). You can agree to disagree and move on with your life.


  • To me the bigger problem is the fact we don’t have a written standard. Idc what people say, but if you buy a 10TB hard drive, then plug it in and the OS doesn’t show 10TB, then it can be easy to blame the drive manufacturer when the OS is just using a different prefix quantity, but calling it the same. There should be some way to know exactly how many bytes there are on a drive before you buy it, and it should match when you plug it into your computer. I don’t think that’s crazy, but the article is a little overboard for that sentiment