3064: Lungfish - Revision history

85.76.106.85: /* Explanation */

2025-12-15T17:33:13Z

‎Explanation

FaviFake: Undo revision 383260 by 207.195.86.129 (talk) From the [[explain xkcd:Editor FAQ#citation|Editor FAQ § [Citation needed]:]] "This template should only be placed when there is a deeper

2025-08-05T11:34:23Z

Undo revision 383260 by 207.195.86.129 (talk) From the Editor FAQ § [Citation needed]: "This template should only be placed when there is a deeper

207.195.86.129: /* Explanation */

2025-08-04T23:29:24Z

‎Explanation

207.195.86.129: /* Explanation */

2025-08-04T23:28:18Z

‎Explanation

FaviFake: /* Explanation */

2025-06-16T20:29:51Z

‎Explanation

FaviFake: /* Explanation */ complete

2025-06-16T13:56:55Z

‎Explanation: complete

FaviFake: /* Explanation */

2025-06-16T13:56:37Z

‎Explanation

162.158.108.109: /* Explanation */ Reduce lots of extra

2025-03-28T06:52:20Z

‎Explanation: Reduce lots of extra

172.71.255.90: artefacts -> artifacts (typo fix)

2025-03-20T19:12:04Z

artefacts -> artifacts (typo fix)

172.71.241.78: Undo revision 369575 by 141.101.76.72 (talk) This is not so complicated as too need headers (see most other articles!), and not enough care in typing "Biology" correctly.

2025-03-20T16:08:14Z

Undo revision 369575 by 141.101.76.72 (talk) This is not so complicated as too need headers (see most other articles!), and not enough care in typing "Biology" correctly.

@@ Line 12: / Line 12: @@
 {{w|Lungfish}} have the largest known {{w|genome}} among the {{w|vertebrate}}s (133 billion {{w|base pair}}s), and the third-largest known genome of all species. The comic relates this to a common issue when editing documents or coding, where the author accidentally makes changes to {{w|Fork (software development)|two separately created versions of documents}}, when they meant to only edit one, which can result in changes to both (or all) resulting documents becoming functionally essential parts of the completed project, or at least present as development artifacts in the 'final' product. This may happen if documents are sent for review (or updating) to different editors, or at different times, and the changes from the earlier one(s) aren't properly integrated with the later one(s). The comic posits that Lungfish has a habit of doing this with its own genome, making both genes essential and increasing the amount of base pairs.
-When Cueball confronts Lungfish about this bad habit of mismanaging its genome, Lungfish dismisses him by saying he'll just "buy more storage". This is likely alluding to when people are faced with an increasing number of files on their storage media, they just buy more storage, either by adding another media drive or paying additional monthly fees for online storage (ex: [https://www.apple.com/ca/icloud/ iCloud] or [https://one.google.com/about/plans Google Drive]). Because of the relatively low cost of storage, this often seems like any easy 'solution', but doesn't actually address the problems of information fragmentation and management. As well as being an issue in their [[1718: Backups| own right]], a failure to deal with these can lead to a repeating pattern that ratchets up storage cost over time. If part of the process is to buy 'fresh' storage space, perhaps to ''attempt'' to rationalise the new and historic files from where they were previously, an even worse legacy of 'temporary' copies (or near-copies) of old files may end up littering [[1360: Old Files|various layers of storage]], in ways that may later confuse matters further.
+When Cueball confronts Lungfish about this bad habit of mismanaging its genome, Lungfish dismisses him by saying it'll just "buy more storage". This is likely alluding to when people are faced with an increasing number of files on their storage media, they just buy more storage, either by adding another media drive or paying additional monthly fees for online storage (ex: [https://www.apple.com/ca/icloud/ iCloud] or [https://one.google.com/about/plans Google Drive]). Because of the relatively low cost of storage, this often seems like any easy 'solution', but doesn't actually address the problems of information fragmentation and management. As well as being an issue in their [[1718: Backups| own right]], a failure to deal with these can lead to a repeating pattern that ratchets up storage cost over time. If part of the process is to buy 'fresh' storage space, perhaps to ''attempt'' to rationalise the new and historic files from where they were previously, an even worse legacy of 'temporary' copies (or near-copies) of old files may end up littering [[1360: Old Files|various layers of storage]], in ways that may later confuse matters further.
 The lungfish's file names ''Copy of Copy of Gene v3 (Newest) (2)'' and ''Copy of Copy of Gene v3 (Final) (2)'' strongly hint at a very poorly organized method of version tracking, as especially evidenced by both existing as 'current' versions, with a tendency of the lungfish to 'copy-paste' inconsistently, certainly explaining why it keeps editing and maintaining multiple genes instead of a single one. These inconsistencies are usually caused by:

@@ Line 34: / Line 34: @@
 : Some users will keep older and newer drafts of a file in case of a need to revert back to an older version. This can be done with a number label (i.e. "v1", "v2", etc.) or a proper word (i.e. "draft", "edited", etc.). This is often entirely at the user's discretion. If well-defined, this can be useful. If an edit breaks something important or with mistaken saves, this can recover lost data. But it can also lead to file hoarding and revisiting older documents by accident. Such a manual method of attempting to keep sequential versions in line can easily be open to misuse and ambiguity of status.
-Obviously{{citation needed}}, [https://www.science.org/content/article/odd-fish-has-30-times-much-dna-humans-new-record-animals this is not why lungfish have a large genome]. While some organisms do contain many copies of genes as a diversification strategy, this mostly occurs only in some plants and single-celled {{w|eukaryotes}}. Lungfish have roughly the same number of genes as a human (and likely slightly fewer), and the large size of the lungfish genome is likely due to poor {{w|transposon}} control causing their chromosomes to fill up with junk.
+However, [https://www.science.org/content/article/odd-fish-has-30-times-much-dna-humans-new-record-animals this is not why lungfish have a large genome]. While some organisms do contain many copies of genes as a diversification strategy, this mostly occurs only in some plants and single-celled {{w|eukaryotes}}. Lungfish have roughly the same number of genes as a human (and likely slightly fewer), and the large size of the lungfish genome is likely due to poor {{w|transposon}} control causing their chromosomes to fill up with junk.
 The title text further compares the biology of lungfish to managing versions of files in a popular version control system called {{w|Git}}. Git includes a symbolic reference called [https://www.geeksforgeeks.org/git-head/ "HEAD"] that assists in keeping track of the version of a set of project resources that are being worked on in a particular repository; HEAD is intended to point to the branch in change history where new changes will be recorded. Rebasing, in Git, is the act of editing the lineage of project file changes in order to present a simplified history, instead of accumulating changes as they actually occurred, which may be messy. Cueball says this process is complicated due to the large number of 'base pairs' - a pun since base pairs are elements of genes, while the 'base' in file change history refers to an ancestral version of a file to which changes have been applied. {{w|Bilateria}} is a clade of animals characterized by embryonic bilateral symmetry, giving their bodies distinguishable "head" and "tail" ends. Since this applies to lungfish, Cueball says, in another pun, that the lungfish should at least know how to use the "head" reference in Git.

@@ Line 30: / Line 30: @@
 :* If multiple files are renamed at once, all of the files will be given the same name with a number label.
-; "v3"
+; "v3, (Newest), (Final)"
 : Some users will keep older and newer drafts of a file in case of a need to revert back to an older version. This can be done with a number label (i.e. "v1", "v2", etc.) or a proper word (i.e. "draft", "edited", etc.). This is often entirely at the user's discretion. If well-defined, this can be useful. If an edit breaks something important or with mistaken saves, this can recover lost data. But it can also lead to file hoarding and revisiting older documents by accident. Such a manual method of attempting to keep sequential versions in line can easily be open to misuse and ambiguity of status.

@@ Line 34: / Line 34: @@
 : Some users will keep older and newer drafts of a file in case of a need to revert back to an older version. This can be done with a number label (i.e. "v1", "v2", etc.) or a proper word (i.e. "draft", "edited", etc.). This is often entirely at the user's discretion. If well-defined, this can be useful. If an edit breaks something important or with mistaken saves, this can recover lost data. But it can also lead to file hoarding and revisiting older documents by accident. Such a manual method of attempting to keep sequential versions in line can easily be open to misuse and ambiguity of status.
-However, [https://www.science.org/content/article/odd-fish-has-30-times-much-dna-humans-new-record-animals this is not why lungfish have a large genome]. While some organisms do contain many copies of genes as a diversification strategy, this mostly occurs only in some plants and single-celled {{w|eukaryotes}}. Lungfish have roughly the same number of genes as a human (and likely slightly fewer), and the large size of the lungfish genome is likely due to poor {{w|transposon}} control causing their chromosomes to fill up with junk.
+Obviously{{citation needed}}, [https://www.science.org/content/article/odd-fish-has-30-times-much-dna-humans-new-record-animals this is not why lungfish have a large genome]. While some organisms do contain many copies of genes as a diversification strategy, this mostly occurs only in some plants and single-celled {{w|eukaryotes}}. Lungfish have roughly the same number of genes as a human (and likely slightly fewer), and the large size of the lungfish genome is likely due to poor {{w|transposon}} control causing their chromosomes to fill up with junk.
 The title text further compares the biology of lungfish to managing versions of files in a popular version control system called {{w|Git}}. Git includes a symbolic reference called [https://www.geeksforgeeks.org/git-head/ "HEAD"] that assists in keeping track of the version of a set of project resources that are being worked on in a particular repository; HEAD is intended to point to the branch in change history where new changes will be recorded. Rebasing, in Git, is the act of editing the lineage of project file changes in order to present a simplified history, instead of accumulating changes as they actually occurred, which may be messy. Cueball says this process is complicated due to the large number of 'base pairs' - a pun since base pairs are elements of genes, while the 'base' in file change history refers to an ancestral version of a file to which changes have been applied. {{w|Bilateria}} is a clade of animals characterized by embryonic bilateral symmetry, giving their bodies distinguishable "head" and "tail" ends. Since this applies to lungfish, Cueball says, in another pun, that the lungfish should at least know how to use the "head" reference in Git.

@@ Line 24: / Line 24: @@
 : Numbered labels in brackets can be produced by a couple different actions:
-* If a file is downloaded from a webpage (such as webmail, or intranet/internet repository) and a file with same name already exists in the download folder, most modern browsers similarly append a number such as "(1)", or other number, as necessary.
+:* If a file is downloaded from a webpage (such as webmail, or intranet/internet repository) and a file with same name already exists in the download folder, most modern browsers similarly append a number such as "(1)", or other number, as necessary.
-* If a copied file is pasted multiple times into the same folder, it will also receive number labels in the same format. This includes copies that are also appended as such in the above points, so a newly-pasted file might end up with a "Copy of" prefix AND a "(2)" suffix, or the next available value that does not clash with documents currently held in the same location.
+:* If a copied file is pasted multiple times into the same folder, it will also receive number labels in the same format. This includes copies that are also appended as such in the above points, so a newly-pasted file might end up with a "Copy of" prefix AND a "(2)" suffix, or the next available value that does not clash with documents currently held in the same location.
-* If multiple files are renamed at once, all of the files will be given the same name with a number label.
+:* If multiple files are renamed at once, all of the files will be given the same name with a number label.
 ; "v3"

@@ Line 10: / Line 10: @@
 ==Explanation==
-{{incomplete|It looks mostly sound, but could use an authority to sign off before clearing the tag.}}
+{{w|Lungfish}} have the largest known {{w|genome}} among the {{w|vertebrate}}s (133 billion {{w|base pair}}s), and the third-largest known genome of all species. The comic relates this to a common issue when editing documents or coding, where the author accidentally makes changes to {{w|Fork (software development)|two separately created versions of documents}}, when they meant to only edit one, which can result in changes to both (or all) resulting documents becoming functionally essential parts of the completed project, or at least present as development artifacts in the 'final' product. This may happen if documents are sent for review (or updating) to different editors, or at different times, and the changes from the earlier one(s) aren't properly integrated with the later one(s). The comic posits that Lungfish has a habit of doing this with its own genome, making both genes essential and increasing the amount of base pairs.
 When Cueball confronts Lungfish about this bad habit of mismanaging its genome, Lungfish dismisses him by saying he'll just "buy more storage". This is likely alluding to when people are faced with an increasing number of files on their storage media, they just buy more storage, either by adding another media drive or paying additional monthly fees for online storage (ex: [https://www.apple.com/ca/icloud/ iCloud] or [https://one.google.com/about/plans Google Drive]). Because of the relatively low cost of storage, this often seems like any easy 'solution', but doesn't actually address the problems of information fragmentation and management. As well as being an issue in their [[1718: Backups| own right]], a failure to deal with these can lead to a repeating pattern that ratchets up storage cost over time. If part of the process is to buy 'fresh' storage space, perhaps to ''attempt'' to rationalise the new and historic files from where they were previously, an even worse legacy of 'temporary' copies (or near-copies) of old files may end up littering [[1360: Old Files|various layers of storage]], in ways that may later confuse matters further.

@@ Line 10: / Line 10: @@
 ==Explanation==
-{{incomplete|Created by a COPY OF COPY OF COPY OF COPY OF LUNGFISH v1.0 (FINAL - FOR REVIEW) - looks mostly sound, but could probably use an authority to sign off before clearing the tag.}}
+{{incomplete|It looks mostly sound, but could use an authority to sign off before clearing the tag.}}
 {{w|Lungfish}} (the class ''Dipnoi'') have the largest known {{w|genome}} among the {{w|vertebrate}}s (133 billion {{w|base pair}}s), and the third-largest known genome of all species. The comic relates this to a common issue when editing documents or coding, where the author accidentally makes changes to {{w|Fork (software development)|two separately created versions of documents}}, when they meant to only edit one, which can result in changes to both (or all) resulting documents becoming functionally essential parts of the completed project, or at least present as development artifacts in the 'final' product. This may happen if documents are sent for review (or updating) to different editors, or at different times, and the changes from the earlier one(s) aren't properly integrated with the later one(s). The comic posits that Lungfish has a habit of doing this with its own genome, making both genes essential and increasing the amount of base pairs.
@@ Line 16: / Line 16: @@
 When Cueball confronts Lungfish about this bad habit of mismanaging its genome, Lungfish dismisses him by saying he'll just "buy more storage". This is likely alluding to when people are faced with an increasing number of files on their storage media, they just buy more storage, either by adding another media drive or paying additional monthly fees for online storage (ex: [https://www.apple.com/ca/icloud/ iCloud] or [https://one.google.com/about/plans Google Drive]). Because of the relatively low cost of storage, this often seems like any easy 'solution', but doesn't actually address the problems of information fragmentation and management. As well as being an issue in their [[1718: Backups| own right]], a failure to deal with these can lead to a repeating pattern that ratchets up storage cost over time. If part of the process is to buy 'fresh' storage space, perhaps to ''attempt'' to rationalise the new and historic files from where they were previously, an even worse legacy of 'temporary' copies (or near-copies) of old files may end up littering [[1360: Old Files|various layers of storage]], in ways that may later confuse matters further.
-The names of the "files" reference several things about computer files:
+The lungfish's file names ''Copy of Copy of Gene v3 (Newest) (2)'' and ''Copy of Copy of Gene v3 (Final) (2)'' strongly hint at a very poorly organized method of version tracking, as especially evidenced by both existing as 'current' versions, with a tendency of the lungfish to 'copy-paste' inconsistently, certainly explaining why it keeps editing and maintaining multiple genes instead of a single one. These inconsistencies are usually caused by:
-In short, the file names "Copy of Copy of Gene v3 (Newest) (2)" and "Copy of Copy of Gene v3 (Final) (2)" strongly hint at a very poorly organized method of version tracking, as especially evidenced by both existing as 'current' versions, with a tendency of the lungfish to 'copy-paste' inconsistently, certainly explaining why it keeps editing and maintaining multiple genes instead of a single one.
+; "Copy of"
-However, [https://www.science.org/content/article/odd-fish-has-30-times-much-dna-humans-new-record-animals this is absolutely not why lungfish have a large genome]. While some organisms do contain many copies of genes as a diversification strategy, this mostly occurs only in some plants and single-celled {{w|eukaryotes}}. Lungfish have roughly the same number of genes as a human (and likely slightly fewer), and the large size of the lungfish genome is likely due to poor {{w|transposon}} control causing their chromosomes to fill up with junk.
+: Older versions of Windows, when copy-and-pasting a file within the same folder, would automatically add "Copy of" to the beginning of the filename, resulting in a file named "Copy of ''x''". If the resulting file were then copied, it would be likewise prepended, thus producing "Copy of Copy of ''x''". Newer versions of Windows instead add "- Copy" to the end of filename, which produces the same effect but keeps things in roughly the same order when sorted by name. Other systems may apply their own conventions that interact badly (or fail to sensibly do so) as duplicated and manually renamed files are accessed across differing systems with differing conventions. This was previously referenced in the title text of [[1459: Documents]].
 The title text further compares the biology of lungfish to managing versions of files in a popular version control system called {{w|Git}}. Git includes a symbolic reference called [https://www.geeksforgeeks.org/git-head/ "HEAD"] that assists in keeping track of the version of a set of project resources that are being worked on in a particular repository; HEAD is intended to point to the branch in change history where new changes will be recorded. Rebasing, in Git, is the act of editing the lineage of project file changes in order to present a simplified history, instead of accumulating changes as they actually occurred, which may be messy. Cueball says this process is complicated due to the large number of 'base pairs' - a pun since base pairs are elements of genes, while the 'base' in file change history refers to an ancestral version of a file to which changes have been applied. {{w|Bilateria}} is a clade of animals characterized by embryonic bilateral symmetry, giving their bodies distinguishable "head" and "tail" ends. Since this applies to lungfish, Cueball says, in another pun, that the lungfish should at least know how to use the "head" reference in Git.

@@ Line 17: / Line 17: @@
 The names of the "files" reference several things about computer files:
-* Older versions of Windows, when copy-and-pasting a file within the same folder, would automatically add "Copy of" to the beginning of the filename, resulting in a file named "Copy of ''x''". (This was previously referenced in the title text of [[1459: Documents]].) If the resulting file was then copied, it would be likewise prepended, thus producing "Copy of Copy of ''x''". Newer versions of Windows instead add "- Copy" to the end of filename, which produces the same effect but keeps things in roughly the same order when sorted by name. Google Docs automatically prepends "Copy of ''x''" to document names when copied. Other systems may apply their own conventions<!-- was hoping to add a link to a picture of the situation shown in https://www.facebook.com/groups/it.humor.and.memes/posts/28939508882314854/ - but there's nasty "please login to Facebook" pester-popovers for me, on that... Maybe find a better one later --> that interact badly (or fail to sensibly do so) as duplicated and manually renamed files are accessed across differing systems with differing conventions.
+* Older versions of Windows, when copy-and-pasting a file within the same folder, would automatically add "Copy of" to the beginning of the filename, resulting in a file named "Copy of ''x''". (This was previously referenced in the title text of [[1459: Documents]].) If the resulting file was then copied, it would be likewise prepended, thus producing "Copy of Copy of ''x''". Newer versions of Windows instead add "- Copy" to the end of filename, which produces the same effect but keeps things in roughly the same order when sorted by name. Other systems may apply their own conventions that interact badly (or fail to sensibly do so) as duplicated and manually renamed files are accessed across differing systems with differing conventions.
 * Numbered labels in brackets can be produced by a couple different actions:
-** If multiple files are highlighted and a Rename action is performed, all of the files will be given the same name with a number label, starting with the one clicked on for the Rename action and then proceeding from the top of the list down as originally sorted. For example, if three files named "Alpha", "Beta", and "Gamma" are highlighted, and the user right-clicks on "Gamma" and renames it to "Alphabet", then "Gamma" will be renamed to "Alphabet (1)", followed by "Alphabet (2)" [formerly Alpha] and "Alphabet (3)" [formerly Beta].
+** If multiple files are renamed at once, all of the files will be given the same name with a number label.
 ** If a copied file is pasted multiple times into the same folder, it will also receive number labels in the same format. This includes copies that are also appended as such in the above points, so a newly-pasted file might end up with a "Copy of" prefix AND a "(2)" suffix, or the next available value that does not clash with documents currently held in the same location.
 ** If a file is downloaded from a web-page (such as webmail, or intranet/internet repository) and a file with same name already exists in the download folder, most modern browsers similarly append a number such as "(1)", or other number as necessary.
-* Some users will keep older and newer drafts of a file in case of a need to revert back to an older version. This can be done with a number label (i.e. "v1", "v2", etc.) or a proper word (i.e. "draft", "edited", etc.). This is often entirely at the user's discretion; there may be conventions or even official team policies to follow, but it relies upon editors sticking to those. If well-defined, this can be useful if it's discovered that an edit breaks something important, or in the event that a mistaken save loses data, but it can also lead to file hoarding and the possibility of revisiting older documents when newer ones aren't more obviously available. The version naming is also far from foolproof, as a "(Newest)"-named file can't itself know when it is superseded (perhaps by a "(Final)" file) and even a "(Final)" one cannot be sure that the project hasn't been revisited (perhaps with an update to "(Newest)"). Such a manual method of attempting to keep sequential versions in line can easily be open to misuse and ambiguity of status, especially when any changes have apparently not been so obviously important to the person(s) involved that it has had no "version number" updated — or else ''both'' were (separate!) refinements of some "v2" revision(s), or earlier, without proper regard/awareness of the other update.
+* Some users will keep older and newer drafts of a file in case of a need to revert back to an older version. This can be done with a number label (i.e. "v1", "v2", etc.) or a proper word (i.e. "draft", "edited", etc.). This is often entirely at the user's discretion. If well-defined, this can be useful. If an edit breaks something important or with mistaken saves, this can recover lost data. But it can also lead to file hoarding and revisiting older documents by accident. Such a manual method of attempting to keep sequential versions in line can easily be open to misuse and ambiguity of status.
 In short, the file names "Copy of Copy of Gene v3 (Newest) (2)" and "Copy of Copy of Gene v3 (Final) (2)" strongly hint at a very poorly organized method of version tracking, as especially evidenced by both existing as 'current' versions, with a tendency of the lungfish to 'copy-paste' inconsistently, certainly explaining why it keeps editing and maintaining multiple genes instead of a single one.
-For anyone curious about the science, it's important to note that [https://www.science.org/content/article/odd-fish-has-30-times-much-dna-humans-new-record-animals this is absolutely not why lungfish have a large genome]. While some organisms do contain many copies of genes as a diversification strategy, this mostly occurs only in some plants and single-celled {{w|eukaryotes}}. Lungfish have roughly the same number of genes as a human (and likely slightly fewer), and the large size of the lungfish genome is likely due to poor {{w|transposon}} control causing their chromosomes to fill up with junk.
+However, [https://www.science.org/content/article/odd-fish-has-30-times-much-dna-humans-new-record-animals this is absolutely not why lungfish have a large genome]. While some organisms do contain many copies of genes as a diversification strategy, this mostly occurs only in some plants and single-celled {{w|eukaryotes}}. Lungfish have roughly the same number of genes as a human (and likely slightly fewer), and the large size of the lungfish genome is likely due to poor {{w|transposon}} control causing their chromosomes to fill up with junk.
 The title text further compares the biology of lungfish to managing versions of files in a popular version control system called {{w|Git}}. Git includes a symbolic reference called [https://www.geeksforgeeks.org/git-head/ "HEAD"] that assists in keeping track of the version of a set of project resources that are being worked on in a particular repository; HEAD is intended to point to the branch in change history where new changes will be recorded. Rebasing, in Git, is the act of editing the lineage of project file changes in order to present a simplified history, instead of accumulating changes as they actually occurred, which may be messy. Cueball says this process is complicated due to the large number of 'base pairs' - a pun since base pairs are elements of genes, while the 'base' in file change history refers to an ancestral version of a file to which changes have been applied. {{w|Bilateria}} is a clade of animals characterized by embryonic bilateral symmetry, giving their bodies distinguishable "head" and "tail" ends. Since this applies to lungfish, Cueball says, in another pun, that the lungfish should at least know how to use the "head" reference in Git.