| Revision as of 19:24, 24 December 2022 editKbrose (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers28,038 edits Undid revision 1129328686 by Locke Cole (talk)Tag: Undo← Previous edit |
Latest revision as of 20:22, 22 December 2024 edit undoTom94022 (talk | contribs)Extended confirmed users8,105 edits →Multiple of a unit of measurement by an integer power of two??: Are they positive integer powers of 1024? |
| (29 intermediate revisions by 17 users not shown) |
| Line 1: |
Line 1: |
|
{{Talk header}} |
|
{{Talk header}} |
|
|
{{WikiProject banner shell|class=B| |
|
<!-- Please make your edits below the TOC line, or better yet, add a new section --> |
|
|
{{WPMeasure|class=B|importance=Mid |
|
{{WikiProject Measurement|importance=Mid |
|
| b1 <!--Referencing & citations--> = yes |
|
| b1 <!--Referencing & citations--> = yes |
|
| b2 <!--Coverage and accuracy --> = yes |
|
| b2 <!--Coverage and accuracy --> = yes |
| Line 9: |
Line 9: |
|
| b6 <!--Accessible --> = yes |
|
| b6 <!--Accessible --> = yes |
|
}} |
|
}} |
|
{{WikiProject Computing|class=B|importance=high|software=yes|hardware=yes|hardware-importance=high}} |
|
{{WikiProject Computing|importance=high|software=yes|hardware=yes|hardware-importance=high}} |
|
|
}} |
|
|
<!-- Please make your edits below the TOC line, or better yet, add a new section --> |
|
{{Selfref|For guidelines on using binary prefixes on Misplaced Pages, see ].}} |
|
{{Selfref|For guidelines on using binary prefixes on Misplaced Pages, see ].}} |
|
{{archives|index=/Archive index}} |
|
{{archives|index=/Archive index}} |
| Line 15: |
Line 17: |
|
|archiveheader = {{talkarchivenav}} |
|
|archiveheader = {{talkarchivenav}} |
|
|maxarchivesize = 150K |
|
|maxarchivesize = 150K |
|
|counter = 17 |
|
|counter = 18 |
|
|minthreadsleft = 1 |
|
|minthreadsleft = 1 |
|
|minthreadstoarchive = 1 |
|
|minthreadstoarchive = 1 |
| Line 32: |
Line 34: |
|
|} |
|
|} |
|
|
|
|
|
|
== Multiple of a unit of measurement by an integer power of two?? == |
|
== Remove NPOV tag == |
|
|
|
|
|
FWIW I see little if any POV in the article. {{ping|Locke Cole}} added the NPOV tag without initiating a talk discussion; in accordance with paragraph 4 of ] such a tag may be removed. Unless there is such a talk initiated in the next day or so identifying specific POV I will remove the tag. ] (]) 06:24, 21 December 2022 (UTC) |
|
|
:Yup. I'd have to suggest that any reader coming across an NPOV tag on an article on this subject would be utterly baffled. Tags aren't a mark of shame, they are intended to initiate discussion about specific issues within an article. ] (]) 06:54, 21 December 2022 (UTC) |
|
|
:{{reply|Tom94022}} I've removed the template as the issue has, for the moment, been resolved. —] • ] • ] 07:26, 21 December 2022 (UTC) |
|
|
::There is no consensus for (or a ) it so I it. Specific problems with it include |
|
|
::* Confusing mention of metric prefixes in the lede of an article about binary prefixes. |
|
|
::* Change of name of one the columns to "JEDEC" without consensus. |
|
|
::* Listing of 'tera' as a JEDEC prefix (tera is not defined by JEDEC) |
|
|
:: I can see the template being included further down the page, when binary prefixes are compared with metric ones. |
|
|
::] (]) 08:42, 21 December 2022 (UTC) |
|
|
:::I added the template at a more appropriate location, which resolves the first of the 3 bullets. The other remain unaddressed, but editors {{u|NebY}} and {{u|Headbomb}} discourage discussion of the JEDEC column. Perhaps they can explain why. ] (]) 09:00, 21 December 2022 (UTC) |
|
|
:::I agree, there is no consensus... no consensus for removing the template that has been on this article for over ten years. Get consensus for ''that'' before removing it again. —] • ] • ] 16:35, 21 December 2022 (UTC) |
|
|
|
|
|
Pinging all who contributed to ] at bits template |
|
|
{{ping|Headbomb}} |
|
|
{{ping|Jc37}} |
|
|
{{ping|kbrose}} |
|
|
{{ping|Locke Cole}} |
|
|
{{ping|NebY}} |
|
|
] (]) 09:06, 21 December 2022 (UTC) |
|
|
:A POV tag is not appropriate just because IEC warriors refuse to use the template. Reverted to consensus version.  <span style="font-variant:small-caps; whitespace:nowrap;">] {] · ] · ] · ]}</span> 12:24, 21 December 2022 (UTC) |
|
|
::Cut the childish bullshit about "IEC warriors" (if you bothered to read the article you would see the template is used) and present a case for including decimal prefixes in the ''lede'' of an article about binary prefixes. ] (]) 12:51, 21 December 2022 (UTC) |
|
|
::Decimal prefixes are ''already in the lead''. Second paragraph, even. As to {{tqq|IEC warriors}}, could you explain what someone is to think about the edit history at {{lu|Thunderbird2/The case against deprecation of IEC prefixes}}? you've made over 400 edits as Dondervogel 2, and over 100 edits as Thunderbird2. You make around 20-40 edits to that page ''each year'' going back over a decade. Can you explain how someone seeing that ''wouldn't'' think you were pushing an agenda or a POV? —] • ] • ] 16:41, 21 December 2022 (UTC) |
|
|
:::{{u|Tom94022}} and I worked on that essay. I didn't know that there was a rule against writing or maintaining an essay, nor against holding an opinion about the contents of an essay, whether for or against. ] (]) 17:34, 21 December 2022 (UTC) |
|
|
|
|
|
If the intention here is to return to edit-warring, and to vacuous discussions about 'consensus' along with RfCs that weren't even notified on the talk pages they affected, it would seem to me that the only appropriate course of action is to return to ANI, and call for topic bans all round. I suspect the communities tolerance may be running thin. |
|
|
|
|
|
Alternately, how about those involved each giving a ''simple'' explanation, without reference to 'consensus', RfCs etc, as to ''what exactly this dispute is about''. An explanation that a reader of the article, looking for information on the subject rather than a long history of bickering about number prefixes etc can understand. Anyone incapable of providing such an explanation, in a short paragraph rather than reams of past internal Misplaced Pages history, should probably in the best interests of Misplaced Pages be told to go away, and find another damn hobby. And told to grow up. This vacuous round-in-circles nonsense is simply infantile, and achieves absolutely nothing of benefit to the article, to Misplaced Pages, or to the understanding of what is, after all, an argument about a relatively minor issue in an article on number prefixes, not the history of the Balkans. It isn't complicated. ] (]) 14:23, 21 December 2022 (UTC) |
|
|
|
|
|
:The article is about binary prefixes, and if these are to be summarized in a table in the lead, this table should not include the column of decimal prefixes. Only the two forms of binary prefixes should be presented there. There is no call to transclude a template that is inappropriate in the context. —] 14:40, 21 December 2022 (UTC) |
|
|
|
|
|
::You say 'should not', but can you explain ''why'' it shouldn't also include decimal prefixes, given that a proper understanding of the topic appears to be contingent on understanding that 'kilo', 'mega' etc are being used in two different ways in two different contexts? How does it not benefit the reader to give a simple illustration of what the prefixes mean in these two contexts - the decimal one they are most likely to be familiar with, and the binary one which they may not be? The purpose of this article is to increase understanding of the topic, and I cannot for the life of me see how imparting useful information could not be beneficial. ] (]) 15:03, 21 December 2022 (UTC) |
|
|
:::I agree the template is relevant background, which is why it is . What is the benefit in including the template twice? ] (]) 15:21, 21 December 2022 (UTC) |
|
|
|
|
|
::::Including similar tables twice may well be unnecessary. But if so, why not simply place the complete table at the top of the article, where readers new to the topic will see it, and immediately understand what the topic is about? ] (]) 15:24, 21 December 2022 (UTC) |
|
|
:As the article also references terms that many ''readers'' are familiar with (and that the wide world that is our source still uses dominantly even in new uses) it makes sense to present the kilo/mega/giga terms side-by-side with the "newer" terms. The lead of our article even has this paragraph: |
|
|
::{{tqq|In most contexts, industry uses the multipliers ''kilo'' (''k''), ''mega'' (''M''), ''giga'' (''G''), etc., in a manner consistent with their meaning in the ] (SI), namely as powers of 1000. For example, a 500-gigabyte hard disk holds {{val|500000000000}} bytes, and a 1 Gbit/s (gigabit per second) ] connection transfers data at nominal speed of {{val|1000000000}} bit/s. In contrast with the ''binary prefix'' usage, this use is described as a ''decimal prefix'', as 1000 is a ] (10<sup>3</sup>).}} |
|
|
:which directly references the decimal names/meaning, so the table being present in the lead (in the form of an invocation of the template) makes sense so our readers can see the terms side-by-side and quickly understand the difference. —] • ] • ] 16:02, 21 December 2022 (UTC) |
|
|
::I understand your point but I disagree. The article is about binary prefixes and these should be introduced first, without the complication of decimal prefixes. The comparison should come second. ] (]) 19:21, 21 December 2022 (UTC) |
|
|
:{{u|AndyTheGrump}}, sad to say, you do not seem to have been paying attention. You lost control of this bunch from the start. I answered your question as you asked about my perspective, succinctly and IMO sufficiently. What I refrained from saying was that it got hijacked into an old (and unrelated) fight; none of what followed was "about" or was stated to be to restore the column, only an aggrieved insistence on re-including the controversial template. —] 21:28, 21 December 2022 (UTC) |
|
|
:::I have yet to see any rational explanation of why a template illustrating the topic of this article is 'controversial'. Or, more to the point, why such controversy is of any relevance to the readers of this article. The fact that people keep bringing it up suggests to me that it might be better to find new contributors to work on it - contributors who aren't apparently obsessed with facile arguments serving no useful purpose. If there was politics involved here, or religion, or nationalism. or even support for your local soccer/baseball/whatever teams, I could understand it, but people seem to be arguing just for the sake of it. ] (]) 23:00, 21 December 2022 (UTC) |
|
|
::::Of course, but the objection to introducing these binary prefixes for unambiguous units for storage has indeed been a ''religion'' to a group of vocal and angry editors who find no effort too great to prevent their promulgation or even admission of benefit, when every standards body in the world promotes them, declares old usages deprecated, and a growing body of software vendors implements them to remove the confusion that has persisted throughout the growth of information technology. So, this full table is useful to these ''refuseniks'', because of the last column (JEDEC), to hang on and continue the gaslighting effort in making new readers believe that at least one body (JEDEC) still supports or defines the old usage (which JEDEC does not, in clear language). The opponents however want to remove the table, because they can't seem to get enough courage or support to just remove the misleading last column. This would not be an issue in this trivial situation, if the table did not contain that last column. ] (]) 00:02, 22 December 2022 (UTC) |
|
|
:::::The 'old usage' may well be deprecated, but isn't it something we'd expect at least some of our readers to have encountered? I don't think pretending that prefixes haven't been used that way is helpful to the understanding of the topic. ] (]) 00:21, 22 December 2022 (UTC) |
|
|
::::::Are you under the impression that anyone is trying to remove information about the "old" units, e.g. by mentioning that most standards bodies deprecate them? Is there something wrong with presenting it all in a balanced way? Your earlier characterization of, effectively, religion or sport fanatics is pretty close. BTW, by "cointrovertial" I meant "contested", and meant the template on its own. —] 00:48, 22 December 2022 (UTC) |
|
|
::::::Certainly the old usage is still common and it is not suppressed anywhere. This is indeed discussed in the many articles about the subject matter, and I have observed not a single editor here to just deny that process. These units are often explained and contrasted. It is often documented in great detail. Everyone agrees on that. It is just one side of the issue who does not want to acknowledge the transition to new standards. Misplaced Pages attracts new writers all the time, and often, if not commonly, they want to use new units because they are in fact commonly used in much new software these days, in the most widely distributed operating systems, even. But the soldiers of denial religiously revert the new editor's work to the old ambiguous usage. The censorship is blatant, anti-intellectual, and unencyclopedic. When two new unit prefixes where introduced this fall by the SI, all Misplaced Pages editor were eager and quick to comply and started using them immediately within days, a courtesy not conveyed to the binary prefixes by that group of editors. These are even less know than the binary prefixes. A common (fake) objection always involves that the binary prefixes are not known by most readers. Well, if readers knew everything they would not read Misplaced Pages. But denying new units certainly does not help them learn new things. There is rarely ever anything that is not explained on WP. ] (]) 01:10, 22 December 2022 (UTC) |
|
|
{{od}} |
|
|
Well I didn't expect to set off such a s**tstorm, but now having read thru the above I do suggest that if the JEDEC column is to remain within the template in the lede, then the lede should also have some mention of what JEDEC is, since I suspect it is not a term familiar to the average reader. Perhaps just appending to the 3rd paragraph of the lede something like {{tqq|... these three usages are referred to as a binary prefixes and have been standardized by the ] (JEDEC).}} Note I have spelled out JEDEC as is already done in the lede for SI and IEC. I would also suggest then for consistency we move the links to IEC, SI and JEDEC out of the template.] (]) 00:51, 22 December 2022 (UTC) |
|
|
|
|
|
::Exactly. Only engineers know who or what JEDEC is. Yet, the intent of the column is even obscure, because it lists only three or four prefixes, and the 'old usage' does extend beyond those. In additions, JEDEC makes no claim to these 'definition', they acknowledge the deprecation, and refer to the other standards bodies that have been involved in units. JEDEC does not define or recommend any. They just use the units. Microsoft is the single most visible supported of the old unit usage, and the column could be filled fare deeper based on actual usage. Yet, the column is labeled 'JEDEC'. It should be labeled 'Deprecated' and people would understand it and it would be correct. ] (]) 01:19, 22 December 2022 (UTC) |
|
|
|
|
|
:I support the change to the 3rd paragraph suggested by {{u|Tom94022}}. I'm not sure about removing the links from the template. They made be needed for other uses of the template. ] (]) 01:14, 22 December 2022 (UTC) |
|
|
|
|
|
::Is there any particular reason why we need to use a template at all? Exactly the same information can be conveyed in a custom-made table. ] (]) 01:18, 22 December 2022 (UTC) |
|
|
:::Yes, a local table could be made, but that just increases maintenance effort if the table is used in multiple places. There is also a ] to discuss the JEDEC column at all. IMO it's a better use of editor's time to gain consensus once and then apply the template where it is relevant. ] (]) 01:29, 22 December 2022 (UTC) |
|
|
::::The last attempt to 'gain consensus' didn't seem to work very well. And in any case, templates are supposed to be a means to aid article creation - they aren't supposed to be used to enforce common content where needs may differ. ] (]) 01:39, 22 December 2022 (UTC) |
|
|
:::::Dondervogel 2, I tend to disagree with your assessment, in the current context. These templates have wasted many orders of magnitude more effort and time than individual table creation per article. It is the rare table that makes sense to templatize, because tables are so context-sensitive. And until a template is actually no longer contended, your argument makes no sense. |
|
|
:::::BTW, as a side-comment, use of a template in the MoS has served as a strategy to allow a small group of editors changes of MoS in without debate in the MoS forum. Use of a contested template to dictate MoS is perverse. —] 02:24, 22 December 2022 (UTC) |
|
|
::::::That is exactly why the JEDEC column should be removed, because its content is so specific to a single vendor and has been used to influence opinion just by the type header it is given. Table templates should contain only indisputable facts that cannot be changed or reinterpreted. That's the nature of the other columns in that table. Any deviation from these true standards should be addressed in each article. ] (]) 03:21, 22 December 2022 (UTC) |
|
|
:::::::Using 'K', 'M' etc in the manner described in that column isn't 'specific to a single vendor'. It is a common usage. ] (]) 03:28, 22 December 2022 (UTC) |
|
|
::::::::It's not only common usage, it's the dominant, near universal usage.  <span style="font-variant:small-caps; whitespace:nowrap;">] {] · ] · ] · ]}</span> 04:01, 22 December 2022 (UTC) |
|
|
:::::*{{ping|AndyTheGrump}} The last attempt to find consensus failed because the ] was ill-conceived. There were too many questions posed at once and the questions were posed without prior discussion. There were too many options, an option favoured by some editors was omitted, and the responses to which depended on the selected outcome of another. It was also peppered by childish contributions from editors bringing up issues that were unrelated to the RfC. I tried unsuccessfully to simplify the RfC by removing some of the options that seemed least likely to succeed, so we could focus on the others. |
|
|
:::::*The failure to achieve consensus does not make the problem go away. {{u|Quondum}}'s view is that the templates are not useful, presumably with the intention that individual articles make their own tables, and their own choices. My point is that this multiplies the number of debates by the number of pages. If that is the consensus, so be it. Is it? |
|
|
:::::*The question I wanted to settle (after the RfC closed) was where to discuss a content dispute at ]. Should it be at the talk page of that article or where the discussion on the 3 templates has been centralised for over a year. Several think it is better not to discuss where to debate, and yet here they are debating the same issues on yet another page. |
|
|
:::::*For pages that choose to go their own way, there is no need to centralise the debate. For pages that prefer to use the template, shouldn't there be a centralised location to discuss those templates? |
|
|
:::::] (]) 08:39, 22 December 2022 (UTC) |
|
|
=== Back to the subject article === |
|
|
::::::A template is not policy. A template is not a guideline. A template is not a constituent part of a manual of style. Discussions concerning the content of templates cannot be used to resolve content disputes, because their use cannot be imposed on any particular article. They are a tool for making content creation easier, and that is all they are for - any attempt to use them to enforce particular content, or a particular presentation of content, is an abuse of process. Forget about the damn template, and stick to explaining how adding or excluding specific material in this article aids reader understanding of it. ] (]) 09:02, 22 December 2022 (UTC) |
|
|
:::::::About ] then: |
|
|
:::::::*This article is about binary prefixes, so it should start by explaining what is meant by a binary prefix. Binary prefixes are related to decimal prefixes, so it makes sense to explain how they are related. That should come second. |
|
|
:::::::*The "JEDEC" column is part of explaining binary prefixes, but the name is contentious, and the content of the column depends on the choice of name. The first question is what to call it. Reasonable possibilities for the column header IMO include |
|
|
:::::::# Computer memory (they are used mostly for computer memory) |
|
|
:::::::# Deprecated (because their use is deprecated universally by international standards) |
|
|
:::::::# JEDEC (because JEDEC defines the first three) |
|
|
:::::::# Legacy (the compromise reached at <s>'bits and bytes'</s> ]) |
|
|
:::::::* Unacceptable options that have been proposed include |
|
|
:::::::# Common (because the decimal interpretation is also common) |
|
|
:::::::# Computing (because the decimal interpretation is also widely used in computing, for communications and data storage) |
|
|
:::::::# Customary (because the decimal interpretation was used long before the binary interpretation) |
|
|
:::::::# Traditional (because the decimal interpretation is also traditional) |
|
|
:::::::] (]) 09:55, 22 December 2022 (UTC) |
|
|
::::::::Please can you clarify "Legacy (the compromise reached at 'bits and bytes')"? I haven't found such a compromise prevailing in the history of ] or being reached at ]. Our ] article is about a TV series. Do you mean somewhere else? ] (]) 10:52, 22 December 2022 (UTC) |
|
|
:::::::::The discussion was held at ]. The compromise was reached in November 2021 and implemented in (and similar edits at the 2 sister templates). It lasted about 10 months, until upturned the apple cart, resulting in the present instability. ] (]) 11:13, 22 December 2022 (UTC) |
|
|
::::::::::'''Reality:''' The templates were being actively discussed for many months with no consensus being reached, when you added another proposal during a period of inactivity that was hastily agreed to in less than a week without notifying any of the other editors involved. After said edit was finally noticed many months later it was undone because of the aforementioned lack of notification to other discussion participants. You don't just get to argue indefinitely until you wear your opponents down or catch them missing discussion and get to call that "consensus". I do wish you'd stop casting aspersions and flat out lying about events. —] • ] • ] 16:40, 22 December 2022 (UTC) |
|
|
:::::::::You are correct. The discussion was not at 'bits and bytes' (by which I meant ], but it was not there either). I have now struck out and corrected the misleading text. Apologies for the confusion. ] (]) 11:20, 22 December 2022 (UTC) |
|
|
:::::::{{u|AndyTheGrump}}, just a note on "A template is not a constituent part of a manual of style." Please take a look at ]: {{tl|Bit and byte prefixes}} is transcluded there. Its presence there has been used to argue that it is a constituent part of the MoS. —] 13:40, 22 December 2022 (UTC) |
|
|
::::::::And look where such arguments have got us. A poorly-notified, badly-worded, inconclusive RfC on a template transcluded to a MOS sub-page cannot be used to determine content. The MOS itself cannot be used as such. It is a guideline - one that states, at the top of the page (as with all MOS pages) that it is "best treated with common sense, and occasional exceptions may apply". The purpose of a manual of style (anywhere, not just on Misplaced Pages) is to provide guidance on how subjects are written about. They are not rules restricting content. Using them as such is an abuse of process. ] (]) 15:01, 22 December 2022 (UTC) |
|
|
:::::::::{{smiley}} – agreed. My point is of-topic for this talk page, of course, unless of course someone actually makes an argument such as that this page should look like the MoS, which transcludes the template, or that the template is a guideline because it is part of the MoS. But it should ''not'' be transcluded in the MoS, IMO. But I do not venture into that crowd. —] 15:29, 22 December 2022 (UTC) |
|
|
::::::::::Agreed that it shouldn't be transcluded into the MOS, because it is unhelpful to have MOS text saying one thing beside a table which sometimes contradicts it, depending on how the template's been edited. I've ] but it's met with some opposition. ] (]) 15:46, 22 December 2022 (UTC) |
|
|
:::::::::::Ah, I see, indeed. This is all a bit too surreal for me. I have been caught up in a bigger picture that I've not been following, including people discussing me behind my back in a forum that I have not been watching. —] 16:04, 22 December 2022 (UTC) |
|
|
::::::::::::Just so. Contrariwise, my interest has been in the impact of template changes on the MOS, but now I get pinged to places like this. ] (]) 16:17, 22 December 2022 (UTC) |
|
|
:::::::::::::OK, so I accept responsibility for both sins (opposition at MOS and pinging you here). Here is my position on both |
|
|
:::::::::::::* If there is consensus for creating a bespoke table at MOS I would happily abide by it, but I see no such consensus. My opposition is based on the notion that it is more efficient (better use of volunteer editors' time) to hold one centralised discussion than multiple parallel ones. |
|
|
:::::::::::::* I pinged you here because you consider the content of the JEDEC column ], yet here we are discussing it. You have not explained why it's OK to discuss the JEDEC column here but not there. |
|
|
:::::::::::::] (]) 16:29, 22 December 2022 (UTC) |
|
|
::::::::::::::How about we stop discussing templates and the MOS entirely, and stick to discussing how best to make ''this article'' useful to readers? ] (]) 16:38, 22 December 2022 (UTC) |
|
|
{{od}}Sure. I've lost track of who's for or against what in this article anyway, so I'll just suggest |
|
|
*it's useful to have a table in the lead |
|
|
*the first thing the table should do is show the two sets of symbols for binary prefixes, together with their values |
|
|
*the table should then show the decimal series for comparison and contrast. It's helpful to our readers to provide that grounding and be clear from the start about the difference between binary prefixes, the article's subject, and the decimal prefixes with which most readers will be much more familiar. |
|
|
] (]) 17:25, 22 December 2022 (UTC) |
|
|
|
|
|
:That is precisely my position. ] (]) 17:47, 22 December 2022 (UTC) |
|
|
:That would seem sensible. ] (]) 18:16, 22 December 2022 (UTC) |
|
|
:I agree with the statements listed. —] • ] • ] 15:18, 23 December 2022 (UTC) |
|
|
:Me too ] (]) 18:54, 23 December 2022 (UTC) |
|
|
::FWIW, this template is displayed in relatively few articles, most importantly, this one, ], ] and ]. After the current edit to this article only, the ] article lacks descriptive language for JEDEC in the text of the section displaying the template. The ] text is {{tq2|In some fields of information technology, it has been common to designate non-decimal multiples based on powers of 1024, rather than 1000, for some SI prefixes (kilo-, mega-, giga-), contrary to the definitions in the International System of Units (SI). The SI does not permit the metric prefixes to be used in this conflicting sense. This practice was once sanctioned by some industry associations, including JEDEC.}} which i find rather compelling. Perhaps we should end this discussion here move to the template talk and work on a set of suggested text associated with template explaining the three column headings SI, IEC and JEDEC. If we wish to change JEDEC to something else then the only one I see as reasonable is "Customary" which would be an invented Misplaced Pages word and it along with IEC and SI would have associated text in every article in which the template appears. ] (]) 18:54, 23 December 2022 (UTC) |
|
|
:::This is the talk page for the 'Binary prefix' article. Whether or not we use a template defined elsewhere will be determined by consensus. Here. If you want to engage in discussions regarding a template we are under no obligation to even use, please do so elsewhere. ] (]) 19:02, 23 December 2022 (UTC) |
|
|
::::It seems there is consensus to use the template in this article but at least on editor has issues with the label on one column and maybe those issues may have been resolved by the text added to the lede. So yes we should end this discussion and move any issues with the one column to the template article. If a change is agreed upon there then we can revise all the articles linked. I do think each non-obvious template column heading should be summarized within any using article as in now the case herein - hopefully there is now consensus on that too. ] (]) 19:28, 23 December 2022 (UTC) |
|
|
:::::I can see precisely zero evidence of any such consensus. NebY's proposal above has the support of four different contributors. Nobody so far has opposed it. NebY's proposal refers to a table specific to this article. Not a template. ] (]) 19:43, 23 December 2022 (UTC) |
|
|
::::::A template is a means to an end. The three items {{u|NebY}} listed are all met via the template. There's argument over the ''details'', but there's no need to try to disparage the template. Whether it's raw wikitext tables in the article or the template translucion the core bullet points are addressed. —] • ] • ] 17:27, 24 December 2022 (UTC) |
|
|
:::::::For the purposes of this article, the items three wrong order the template are in. I propose a different order, and that requires a table made for this article. As no-one's said no yet, I'll further suggest |
|
|
:::::::*for binary units, we should show unit names/prefixes, then unit symbols, and finally unit values |
|
|
:::::::*then for decimal units, we should show unit names/prefixes, then symbols, then values |
|
|
:::::::This is the same approach we use in tabulating ] and many, though not all, of our articles about units. ] (]) 17:50, 24 December 2022 (UTC) |
|
|
|
|
|
==JEDEC has not standardized any prefixes or units== |
|
|
In an edit today in the lede of the article it was asserted that JEDEC "has standardized the binary interpretation", which is a statement completely unfounded. JEDEC does not standardize any unit, and explicitly states that the binary interpretation is deprecated, pointing to the proper standards bodies for reference. They explicitly state that the units are only LISTED because of traditional practice. ] (]) 21:14, 22 December 2022 (UTC) |
|
|
|
|
|
:You can quibble about the wording but it remains a fact that ]. It is also a fact that it does not define higher order prefixes. The contested edit should be reinstated IMO. ] (]) 22:04, 22 December 2022 (UTC) |
|
|
::JEDEC ''lists'' the usage, per their own explanation, this does not constitute a definition, just an explanation of common usage, and that without references, btw. Why do you insist on the phrasing ''define''. Going further JEDEC does not ''standardize'', they do the opposite here; they deprecate the usage. Clearly they stopped updating the listings, because they had already deprecated their usage and the higher ones were not common. So there is no justification for that phrasing. And why are these limited JEDEC listings so important to you, to anyone, When the common behavior is to use these unit meaning beyond G? Why don't you want to list the rest? There are certainly references for that that are far more meaningful than the JEDEC papers. ] (]) 22:43, 22 December 2022 (UTC) |
|
|
:::*I use the word "define" because defines '''kilo (K) (as a prefix to units of semiconductor storage capacity)''' as ''A multiplier equal to 1024 (210)'', and similarly for mega and giga. That is not a list. |
|
|
:::*JEDEC is not important, but it is what the template currently uses. Acceptable alternatives include 'Computer memory', 'Deprecated' and 'Legacy'. Use of any one of those would mean we could populate the table to higher orders, which would IMO be more useful for the reader. |
|
|
:::] (]) 23:30, 22 December 2022 (UTC) |
|
|
::::'Deprecated' and 'Legacy' are not acceptable because they are neither deprecated by the industry, nor are they legacy prefixes. Customary would be fine however if we want to expand the table to cover more than just the JEDEC entries.  <span style="font-variant:small-caps; whitespace:nowrap;">] {] · ] · ] · ]}</span> 01:43, 23 December 2022 (UTC) |
|
|
:::::*You might not like it but '''Deprecated''' is accurate (the JEDEC use is deprecated universally by international standards - that's what the word means) and '''Legacy''' is accurate (the JEDEC use remains the norm - that's what the word means). In fact Legacy was used (and stable) for a period of 10 months. |
|
|
:::::* '''Computer memory''' is an option if the table includes decimal prefixes, but would not work in a reduced table, with only binary interpretations. |
|
|
:::::* What is the objection to '''JEDEC''' (stable for years, before the consensus changed to Legacy)? |
|
|
:::::] (]) 09:34, 23 December 2022 (UTC) |
|
|
::::::The word deprecated does not mean deprecated by standards body no one listens to, it means deprecated IRL. And IRL, they aren't deprecated at all. Legacy is also not accurate, because these aren't legacy units at all. They are the modern units everyone save an ''extreme'' minority use.  <span style="font-variant:small-caps; whitespace:nowrap;">] {] · ] · ] · ]}</span> 10:34, 23 December 2022 (UTC) |
|
|
::::::{{tqq|You might not like it but '''Deprecated''' is accurate (the JEDEC use is deprecated universally by international standards - that's what the word means)}} The problem is that a standards body deprecating something when the real world does not puts us in a position of using Misplaced Pages's voice to say something is '''Deprecated''' when it is still in regular and wide use. '''"Deprecated"''' (note the quotes) would be the more accurate shorthand, if and only if we wanted to give these international standards bodies that much weight (a question for ] I'd say considering, again, how rarely used the "standards" are in this instance). {{tqq|What is the objection to '''JEDEC'''}} It incorrectly implies only RAM/memory manufacturers use the terms, when ''many'' other industries still do as well. —] • ] • ] 15:18, 23 December 2022 (UTC) |
|
|
|
|
|
It might be advisable at this point to avoid getting into the minutia of details as to what exactly JEDEC has or hasn't specified until we decide the broader issues regarding the disputed table. ] (]) 22:08, 22 December 2022 (UTC) |
|
|
|
|
|
:As long as JEDEC appears in the template it should be described in the lede so I am going to restore it with the word "defines" instead of "standardized." Details such it was by JEDEC deprecated can be in the body. ] (]) 22:44, 22 December 2022 (UTC) |
|
|
:Maybe the lede now has it backwards - didn't JEDEC just define the terms as used first by semiconductor memory and then picked up by the OSes? So maybe we should resequence the sentence and lead with JEDEC?] (]) 22:50, 22 December 2022 (UTC) |
|
|
|
|
|
::This is not an article about JEDEC. The prefixes in question were in use before the standard concerned was created. Can we please not get involved in yet another discussion about matters not directly related to the article subject itself. Which is binary prefixes themselves, rather than one particular standard that describes them. Sort out the table question first, and maybe we'll get somewhere. ] (]) 23:43, 22 December 2022 (UTC) |
|
|
To solve the issue, I would just remove the JEDEC column altogether. It is redundant. The template is named "Prefixes for multiples of bits (bit) or bytes (B)", not "All prefixes for multiples of bits (bit) or bytes (B)" - as discussed in the text, there were more nomenclature/prefix proposals over time, and if we were heading for completeness in a comparison table we'd have to list them as well - no. Seeing this from a pragmatic point of view, we would not even loose any information as the four entries in the JEDEC column are already present on the left side of the table. Yes, it's labelled "Decimal" there, but everyone who uses kilo to mean 1024 knows that this is "jargon" (though common and convenient) and that the SI strictly defines kilo to mean 1000 only (and never did differently). It's not as if there would be a genuine proposal of some alternative nomenclature to the IEC prefixes which we would have to list in the table - before the IEC prefixes there was just ad-hoc (ab)use of existing nomenclature - and this is discussed in the article already. So, someone looking up the table for a quick check of what was the next prefix in the row after giga, or tera, will still find the info and simply apply the binary meaning to the decimal prefix, like before. Adding the same info in a JEDEC column does not add anything, but create the invalid assumption JEDEC would (have) endorse(d) the usage of the decimal prefixes for binary usage, which they clearly do not (and never did). All the nitty-gritty details regarding JEDEC are (and should) still (be) explained in the body of the article. |
|
|
In addition to solving the issue, this would also remove the somewhat artificial break after tera, make the table somewhat narrower (better flow on mobile devices) and add some nice symmetry to the table, which makes it even easier to "grasp" without having to "decode" the meaning. |
|
|
: --] (]) 10:57, 24 December 2022 (UTC) |
|
|
:::Exactly. I have been advocating for this for a long time. The column makes no sense, is factually wrong and misleading. ] (]) 17:46, 24 December 2022 (UTC) |
|
|
|
|
|
:Unfortunately for binary prefixes the IEC column is the outlier, presenting it in a table like this gives it undue weight on its own considering the overwhelming majority of our sources still use common terms like megabyte, gigabyte, etc. For a detailed look at what our sources say, see ]. —] • ] • ] 17:30, 24 December 2022 (UTC) |
|
|
::Stop the utter nonsense. You are blind because you are prejudiced from the start. The metric usage of the SI prefixes has been the dominant use for decades, outside of some storage, and the IEC prefixes are an international standard now, and are the preferred units for operating system programming in the most widely distributed systems. Today any computer professional or just enthusiast encounters IEC prefixes in use almost hourly in different applications. The standards-correct usage of units is almost pervasive in new software and with open-source software we can actually evaluate this. ] (]) 17:46, 24 December 2022 (UTC) |
|
|
|
|
|
== I give up == |
|
|
|
|
|
I had a vague hope that as an outsider to this article, I might be able to offer something new to the discussion, and in particular to discourage the endless round-in-circles bickering that seems to have become the norm, both here and on related subjects. Clearly I was mistaken, since it appears that many contributors here - quite possibly the majority - are more interested in engaging in endless cycles of vacuous juvenile POV-pushing over the supposed merits of alternative ways of representing numbers than actually fulfilling the supposed objective on an encyclopaedia: to provide an overview of what would seem to be a simple enough topic for readers with varying degrees of prior knowledge. |
|
|
|
|
|
|
My only future involvement in this topic is likely to be in calling for contributors who have acted in such a manner to be topic banned and/or blocked from editing entirely. Wasting your own time is fine, but find somewhere else to do it, where you don't waste other peoples'. Readers deserve better than this. ] (]) 18:25, 24 December 2022 (UTC) |
|
WRT "A binary prefix is a unit prefix that indicates a multiple of a unit of measurement by an integer power of two". Is it? Or is it a power of 1024? Yes, they are all powers of 2, but calling them that seems misleading. That they are power of 2 doesn't seem like the most central defining property of this set of multiples. ] (]) 20:57, 21 December 2024 (UTC) |
|
|
|
|
|
|
: If we had names for other powers of two, they too would be called binary prefixes. The fact that we find only a certain subset of these prefixes convenient enough for general use to create a name does not mean that we should necessarily use the smallest (obvious) category that contains this subset. And no, it is not misleading: it is predicated on the practicality of implementing memory sizes as powers of 2, not of 1024. When the prefixes 'centi', 'deci', 'deca' and 'hecto' fall into disuse, will it be misleading to call the remaining prefixes (all of which are powers of 1000) "decimal prefixes"? (Actually, these are more commonly called "]es", but that is an even vaguer category.) —] 21:13, 21 December 2024 (UTC) |
|
:Yup, as someone who has only been involved in this for a couple of years, it is certainly discouraging seeing some of the arguments used here. For something that should be as simple as just following our reliable sources, it seems to always get turned into what a small fraction of editors "like". Sorry to see you go so soon. —] • ] • ] 18:32, 24 December 2022 (UTC) |
|
|
|
|
|
|
|
::{{ping|Stevebroshar}} has a valid point. ''Binary prefixes'' historically are defined in positive integer powers of 1024 and are likely to continue to do so. They go back to the approximate equivalence of 1,024 to 1,000 and unlike metric prefixes are not defined for each power of the base number to a maximum and not to a minimum at all. Whether the rarely used metric prefixes fall into disuse or not is irrelevant, they would remain defined. I think we would have to find an RS to change the article to state "positive integer powers of 1024" but with one I would support such a such a change. ] (]) 20:22, 22 December 2024 (UTC) |
|
::If you are under the impression that I have found your contributions to this discussion of net benefit, you are mistaken. ] (]) 18:34, 24 December 2022 (UTC) |
|
|
:::Oh, I'm aware. I can still appreciate an uninvolved voice trying to wade into this issue and be sad to see you go, no? —] • ] • ] 18:40, 24 December 2022 (UTC) |
|
WRT "A binary prefix is a unit prefix that indicates a multiple of a unit of measurement by an integer power of two". Is it? Or is it a power of 1024? Yes, they are all powers of 2, but calling them that seems misleading. That they are power of 2 doesn't seem like the most central defining property of this set of multiples. Stevebroshar (talk) 20:57, 21 December 2024 (UTC)
