Editing 1636: XKCD Stack

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 12: Line 12:
 
Another example of a tech stack is featured in [[2166: Stack]].
 
Another example of a tech stack is featured in [[2166: Stack]].
  
===Layers===
+
===Explanation of Layers===
 
;EBNF/CSS
 
;EBNF/CSS
 
:BNF or {{w|Backus–Naur Form}} is a syntax used for describing {{w|context-free grammars}}. {{w|Extended Backus–Naur Form|EBNF}} is "Extended BNF", it is the same thing as BNF with a few more syntactic constructs intended to ease its use in the most common cases. [[1343: Manuals]] mentioned EBNF.
 
:BNF or {{w|Backus–Naur Form}} is a syntax used for describing {{w|context-free grammars}}. {{w|Extended Backus–Naur Form|EBNF}} is "Extended BNF", it is the same thing as BNF with a few more syntactic constructs intended to ease its use in the most common cases. [[1343: Manuals]] mentioned EBNF.
Line 34: Line 34:
 
:Writing any non-trivial piece of software always require a phase of {{w|debugging}}, which consists in finding and fixing {{w|Software bug|bugs}}. With complex software, this is a long and tiring process, so when the product is finally finished no one dares to modify it any further for fear that it will fail in unexpected ways. After some time passes, it is even worse because nobody really remembers how the software was ''supposed'' to work, so the product becomes some kind of godlike treasure which must be treated with the utmost respect and reverence because, you know, if it stops working we're all doomed ([[1421: Future Self]]). After completion, {{w|Refactoring}} is the process of rewriting code for greater efficiency or reliability. However, if the performance is not 'too bad' (i.e. not unusably terrible in normal use) there is a great temptation to avoid this, in favor of the 'if it ain't broke, don't fix it' methodology. This could lead, for example, to a trained monkey and an abacus being used to crunch numbers. It works, but could be done far better. However, nobody wishes to change it, for fear of breaking a presently functional, if inefficient, system.
 
:Writing any non-trivial piece of software always require a phase of {{w|debugging}}, which consists in finding and fixing {{w|Software bug|bugs}}. With complex software, this is a long and tiring process, so when the product is finally finished no one dares to modify it any further for fear that it will fail in unexpected ways. After some time passes, it is even worse because nobody really remembers how the software was ''supposed'' to work, so the product becomes some kind of godlike treasure which must be treated with the utmost respect and reverence because, you know, if it stops working we're all doomed ([[1421: Future Self]]). After completion, {{w|Refactoring}} is the process of rewriting code for greater efficiency or reliability. However, if the performance is not 'too bad' (i.e. not unusably terrible in normal use) there is a great temptation to avoid this, in favor of the 'if it ain't broke, don't fix it' methodology. This could lead, for example, to a trained monkey and an abacus being used to crunch numbers. It works, but could be done far better. However, nobody wishes to change it, for fear of breaking a presently functional, if inefficient, system.
 
;Triply-Nested Docker
 
;Triply-Nested Docker
:{{w|Docker (software)|Docker}} is a {{w|Operating-system-level virtualization|software container}}, which is a way that allows a complete operating system to run under different operating system (OS) (as long they share the same kernel, among other things). Triply-nested docker would mean OS A running under OS B running under OS C running under OS D (running under OS E?). That would likely be a performance and management nightmare.
+
:{{w|Docker (software)|Docker}} is a {{w|Operating-system-level virtualization|software container}}, which is a way that allows a complete operating system to run under different operating system (OS) (as long they share the same kernel, among other things). Triply-nested docker would mean OS A running under OS B running under OS C running under OS D (running under OS E?). That would likely be a performance and management nightmare
 
;Paravirtual Boy®
 
;Paravirtual Boy®
 
:This is a reference to the {{w|Virtual Boy}}, a failed portable console created by {{w|Nintendo}}. It was [https://www.youtube.com/watch?v=MKKK6FH1vGw promoted as being a highly immersive, incredible experience], but the poor technology that it used caused it to be [https://youtu.be/OyVAp0tOk5A?t=56s very criticized] for not meeting the high expectations. {{w|Paravirtualization}} is a way of virtualization, that requires cooperation of the guest operating system, contrary to {{w|full virtualization}}, on which the guest operating system is not required to do anything special and the host handles everything.
 
:This is a reference to the {{w|Virtual Boy}}, a failed portable console created by {{w|Nintendo}}. It was [https://www.youtube.com/watch?v=MKKK6FH1vGw promoted as being a highly immersive, incredible experience], but the poor technology that it used caused it to be [https://youtu.be/OyVAp0tOk5A?t=56s very criticized] for not meeting the high expectations. {{w|Paravirtualization}} is a way of virtualization, that requires cooperation of the guest operating system, contrary to {{w|full virtualization}}, on which the guest operating system is not required to do anything special and the host handles everything.

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)