Editing 2224: Software Updates

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 20: Line 20:
 
Randall argues that in reality, though, because even these traditional pieces of software have versions and are equally susceptible to having a feature axed by the developer, as well as the problems of running increasingly old software - mainly concering bugs and later-discovered security vulnerabilities that would only be patched via upgrades, the practical upshot of these trends is that it's rarely plausible to buy a single copy of software and continue to run it indefinitely. Almost all consumers who continue to use a particular piece of software will eventually need to upgrade to and pay for new versions. While this isn't precisely the same as paying regular licensing fees and running software that automatically updates, it's an effectively similar model. In that sense, "All software is Software as a Service".
 
Randall argues that in reality, though, because even these traditional pieces of software have versions and are equally susceptible to having a feature axed by the developer, as well as the problems of running increasingly old software - mainly concering bugs and later-discovered security vulnerabilities that would only be patched via upgrades, the practical upshot of these trends is that it's rarely plausible to buy a single copy of software and continue to run it indefinitely. Almost all consumers who continue to use a particular piece of software will eventually need to upgrade to and pay for new versions. While this isn't precisely the same as paying regular licensing fees and running software that automatically updates, it's an effectively similar model. In that sense, "All software is Software as a Service".
  
βˆ’
The title text refers to a different aspect of cloud applications. Since they run "in the cloud" on remote computers, they are subject to the limitations of network speed to the servers. The time for data to be sent to a server and a response to be received back is called the "ping time".  
+
The title text refers to a different aspect of cloud applications. Since they run "in the cloud" on remote computers, they are subject to the effects of network speed to the servers. The time for data to be sent to a server and a response to be received back is called the "ping time".  
  
 
Since a "cloud server" is just a computer, there is no fundamental difference between software running remotely and software running locally on a user's computer. The biggest difference is that software running locally will respond almost instantly to user input, whereas software running remotely may take longer to respond, since the data first needs to be sent over a network (the internet), processed, and then sent back to the user's computer. In addition, the chance of data loss (packet loss) may cause the response to be even slower, as data has to be re-sent, or often result in no response at all. Hence, in practice, this can have an enormous impact on the experience of using remote software vs software that runs locally (as anyone who has tried online gaming on a laggy server can attest).  
 
Since a "cloud server" is just a computer, there is no fundamental difference between software running remotely and software running locally on a user's computer. The biggest difference is that software running locally will respond almost instantly to user input, whereas software running remotely may take longer to respond, since the data first needs to be sent over a network (the internet), processed, and then sent back to the user's computer. In addition, the chance of data loss (packet loss) may cause the response to be even slower, as data has to be re-sent, or often result in no response at all. Hence, in practice, this can have an enormous impact on the experience of using remote software vs software that runs locally (as anyone who has tried online gaming on a laggy server can attest).  
Line 29: Line 29:
  
 
==Transcript==
 
==Transcript==
βˆ’
:[A graph with two axes. Over and right of the axes are two labeled arrows pointing along the two axes:]
+
:[A graph with two axis. Over and right of the axis are two labeled arrows pointing along the two axis:]
 
:X-axis: Time  
 
:X-axis: Time  
 
:Y-axis: Software Version Number  
 
:Y-axis: Software Version Number  
  
βˆ’
:[The graph consists of three lines. Two gray lines moves in upwards step from left to right. The upper line begins a bit up the Y-axis, the bottom line begins somewhat down the X-axis. From there both lines move upwards in steps of different height. The distance between them stays on average about the same for the entire graph, but moves from bottom to top of the graph. Labeled arrows point to the top and the bottom gray line. The area between them is shaded light gray and has a gray label written in the middle. The third line is black. It begins from a dot just under the second step in the upper gray line. This line also makes steps, keeping close to the upper line, although it makes fewer steps than that line. But a bit over halfway to the top, it stops stepping, staying on the same level for the rest of the graph; thus eventually it falls outside of the light gray area between the other two lines, where it had been until the bottom line stepped above it. This black line is also labeled, with normal black text written beneath the first full step inside the gray area. There is one other point labeled on the black line: a dot just after the final step, under the next large step in the upper gray line. At the end of the black line there are question marks with an arrow beneath pointing right. The arrow has a label to the left.]
+
:[The graph consist of three lines. Two gray lines moves in upwards step from left to right. The upper line begins a bit up the Y-axis the bottom line begins somewhat down the X-axis. From there both lines move upwards in steps of different height. The distance between them stays on average about the same for the entire graph, but moves from bottom to top of the graph. Labeled arrows point to the top and the bottom gray line. The area between them is shaded light gray and has a gray label written in the middle. The third line is black. It begins from a dot just under the second step in the upper gray line. This line also makes steps, keeping close to the upper line, although it makes fewer step than that line. But a bit over halfway to the top, it stops stepping staying on the same level for the rest of the graph, thus eventually it falls outside of the light gray area between the other two lines, where it had been until the bottom line steps above it. This black line is also labeled, with normal black text written beneath the first full step inside the gray area. Three other points on the black line is also labeled. The starting dot, a second dot just after the final step, under the next large step in the upper gray line, and finally at the end of the black line there are questions mark with an arrow beneath pointing right. The arrow has a label to the left.]
 
:Upper gray line: Newest Version
 
:Upper gray line: Newest Version
 
:Bottom gray line: Oldest Supported Version
 
:Bottom gray line: Oldest Supported Version

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)