| Latest revision |
Your text |
| Line 13: |
Line 13: |
| | | | |
| | :You are right, but I think we should make allowances to the look as this is stated to be an 'industrial' computer. Sebastian --[[Special:Contributions/172.68.110.52|172.68.110.52]] 16:24, 18 September 2017 (UTC) | | :You are right, but I think we should make allowances to the look as this is stated to be an 'industrial' computer. Sebastian --[[Special:Contributions/172.68.110.52|172.68.110.52]] 16:24, 18 September 2017 (UTC) |
| − |
| |
| − | ::Actually I take this unusual look to be quite on purpose: this machine is so unique, in such a specific place doing a specific job, that nobody has tried changing or updating anything in years. It might even take a reboot to spot WHAT is booting up. Hence the situation as it stands, that "new technology takes a while to come to" this computer, as an industry, or a section thereof. [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 04:32, 22 September 2017 (UTC)
| |
| | | | |
| | https://www.cpsc.gov/Safety-Education/Safety-Education-Centers/Fireworks has a link to the 2016 Fireworks Annual Report, which has some useful statistics on page 2, the executive summary. | | https://www.cpsc.gov/Safety-Education/Safety-Education-Centers/Fireworks has a link to the 2016 Fireworks Annual Report, which has some useful statistics on page 2, the executive summary. |
| Line 22: |
Line 20: |
| | | | |
| | What bothers me about old technology is that security updates stop while the rest of the world gains an ever-increasing exploit advantage over people connecting to the same Internet. Along with the risks to them, it's worse when compromised devices act as workhorses to leverage "millions of papercuts" against the rest of the system. [[User:Elvenivle|Elvenivle]] ([[User talk:Elvenivle|talk]]) 00:27, 19 September 2017 (UTC) | | What bothers me about old technology is that security updates stop while the rest of the world gains an ever-increasing exploit advantage over people connecting to the same Internet. Along with the risks to them, it's worse when compromised devices act as workhorses to leverage "millions of papercuts" against the rest of the system. [[User:Elvenivle|Elvenivle]] ([[User talk:Elvenivle|talk]]) 00:27, 19 September 2017 (UTC) |
| − |
| |
| − | : The systems running these old OS versions are generally not connected to the outside world, especially not to the internet. These servers are generally used to control components in the overall system (e.g. start or stop a pump) and have no reason to be connected. In that situation, security updates are far less important, as only a handful of people can even connect to the machine from a private network.
| |
| − | [[Special:Contributions/162.158.111.115|162.158.111.115]] 07:16, 24 September 2017 (UTC)
| |
| − |
| |
| − | :: You'd think (and hope) so, but I've encountered plenty of systems still running Vista and XP with Internet access. What Randall misses with his analogy is that fireworks do not pose any sort of security risk that switching to nuclear weapons negate. [[Special:Contributions/172.68.253.59|172.68.253.59]] 14:57, 19 April 2018 (UTC)
| |
| | | | |
| | Hm, while it makes sense to stick to a DOS based system if nothing newer is required, the comparative of fireworks/nuclear weapons is incorrect. Upgrading those MSDOS systems to something newer (which could be just freedos) would perhaps incur on huge unnecessary expenses at most, while "upgrading" fireworks to nuclear energy would not only would make them far more expensive, it would make them far, far more dangerous and deadly. [[Special:Contributions/162.158.69.123|162.158.69.123]] 00:32, 19 September 2017 (UTC) | | Hm, while it makes sense to stick to a DOS based system if nothing newer is required, the comparative of fireworks/nuclear weapons is incorrect. Upgrading those MSDOS systems to something newer (which could be just freedos) would perhaps incur on huge unnecessary expenses at most, while "upgrading" fireworks to nuclear energy would not only would make them far more expensive, it would make them far, far more dangerous and deadly. [[Special:Contributions/162.158.69.123|162.158.69.123]] 00:32, 19 September 2017 (UTC) |
| Line 38: |
Line 31: |
| | I still use MS-DOS. Unless there's an easier way to get a list of all the files in a folder in text file format. [[Special:Contributions/162.158.155.62|162.158.155.62]] 09:25, 19 September 2017 (UTC) | | I still use MS-DOS. Unless there's an easier way to get a list of all the files in a folder in text file format. [[Special:Contributions/162.158.155.62|162.158.155.62]] 09:25, 19 September 2017 (UTC) |
| | : Is that a joke? Is that a real question? In Windows 10; Win Key, type "command line", press enter to open Command Line. Type "CD <Address>" and press enter, where address is desired address. You can also right-click the address bar of any File Explorer location and choose Copy Address As Text, and just paste it into the address bar. Then type "dir > list.txt". DONE. If you want to trim out the extra information so that it's literally just a list of files with no extra information, like if you want to plug it into a program to process those files, use "dir /b > list.txt". Windows 10 doesn't have DOS. It still supports all the usual basic command line stuff. The ''hardest part'' about doing this in Windows 10 ''is having to install Windows 10''. [[Special:Contributions/162.158.2.106|162.158.2.106]] 11:21, 19 September 2017 (UTC) | | : Is that a joke? Is that a real question? In Windows 10; Win Key, type "command line", press enter to open Command Line. Type "CD <Address>" and press enter, where address is desired address. You can also right-click the address bar of any File Explorer location and choose Copy Address As Text, and just paste it into the address bar. Then type "dir > list.txt". DONE. If you want to trim out the extra information so that it's literally just a list of files with no extra information, like if you want to plug it into a program to process those files, use "dir /b > list.txt". Windows 10 doesn't have DOS. It still supports all the usual basic command line stuff. The ''hardest part'' about doing this in Windows 10 ''is having to install Windows 10''. [[Special:Contributions/162.158.2.106|162.158.2.106]] 11:21, 19 September 2017 (UTC) |
| − | :: I suspect the guy at "162.158.155.62" is the kind of user who confuses the NT's cmd prompt as "MS-DOS" (which is quite common, unfortunately) [[Special:Contributions/162.158.69.159|162.158.69.159]] 08:51, 20 September 2017 (UTC)
| |
| − | ::: No, Command Prompt '''IS''' DOS, essentially, just with a new name. Runs all the same commands in the same way, works the same way. Those of us who remember using MS-DOS have a nice advantage in that environment for this reason. The only differences are subtle and largely internal (the only differences I can think of is that there's an underlying security being applied, hence the existence of "Administrator Command Prompt", and that it isn't the underlying foundation of Windows, that the original phrase, Disk Operating System, is no longer accurate). I believe the name change was mostly just to not scare away people who heard about DOS having a steep learning curve. In fact, having used DOS 5.0, 6.0 and 6.22, I find there's NO difference in the language since 6.22, especially considering the differences between the other versions. Trying to make the point the it isn't DOS is nit picking and helps nothing.
| |
| − | ::: And I agree with 162 158 155 62 here, I use '''DOS''' quite regularly to get file lists. I'm really not sure why Windows has never implemented such functionality. [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 04:32, 22 September 2017 (UTC)
| |
| − | :::: Command prompt runs like DOS, sure. But it's not DOS. This is a comic about '''Obsolete Technology'''. If you're using Command Prompt in a currently supported version of Windows, you're not using '''obsolete''' technology. Command Line will never be an obsolete feature in any OS used by computing enthusiasts - not until we have neural interfaces. MS-DOS - an actual MS-DOS installation - '''is''' obsolete. Windows '''did''' implement such functionality. That's what Command Prompt is for: using the keyboard to call up a ton of functions that are too niche to be in the right-click menu. [[Special:Contributions/162.158.2.106|162.158.2.106]] 16:55, 22 September 2017 (UTC)
| |
| − | ::::: Other than Command Prompt not actually being the foundation of the operating system, I can't find a single difference. The language is the same, the commands are the same, even the command switches are the same. People here are nitpicking nomenclature. I am one of many who find it perfectly acceptable to refer to it as DOS. It seems like using the Command Prompt in Windows should theoretically be unnecessary, that its continued presence is mostly to keep geeks like me happy. As such, actually using it would be thought of as using obsolete technology (not that it '''Is''' obsolete, seems like most if not all of the people in this thread knows of things only possible within Command Prompt). After all, the trend over the last decades is toward "user friendly", starting with hiding DOS away, letting people do things without knowing commands. These days "user friendly" seems to mean "hiding away anything that isn't basic", it's old fashioned to need text commands. If it isn't doable directly in Windows, it's because Microsoft deemed it unnecessary. Besides which, my comments are less about the comic but more about comments here nitpicking other comments. Let people call it DOS and move on, don't get stuck in the muck. That's all I'm really saying. Some people seem to be nitpicking so hard as to actually seem confused, like thinking (or pretending to think) that mentioning using DOS means using a DOS emulator! [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 04:32, 26 September 2017 (UTC)
| |
| − | :::::: And all I was saying, was that someone talking about '''Windows NT Command Line''', in a discussion about obsolete technology, while calling it "DOS", is choosing to be misunderstood. Even if it looks and acts the same for the user, it has completely different code under the hood. It's technology is different. DOS is obsolete because it can't use modern innovations, like more than 4GB of RAM, or USB, or multi-core CPUs. DOS-style commands are an entirely different subject to MS-DOS, the operating system. (And "User Friendly" is literally about making it easier for Novices to use technology. Typing commands is not novice-friendly. If you are an advanced user, command lines are helpful, especially for Admins, but Windows is designed for the average consumer, using as little cerebral overhead as possible, not the advanced users.) [[Special:Contributions/162.158.2.106|162.158.2.106]] 17:35, 23 October 2017 (UTC)
| |
| − | ::::::: ***sigh*** No, actually, as I said, it's people nitpicking nomenclature (that means word choice) are the ones ACTUALLY choosing to misunderstand. All those limitations you listed are part of the operating system, which I've already dismissed as the only real difference between DOS and Command Prompt. So this argument is invalid, ignoring the stipulation already made. The LANGUAGE of Command Prompt is the same as DOS. Which means from a user point of view, they're the damned same. That it "looks and acts the same for the user" is everything, and why such relaxing of terminology is perfectly acceptable! The point of language is to be understood. And, barring people nitpicking and being difficult and purposely misunderstanding, calling it DOS can be easily understood. Mission accomplished. So, again, quit nitpicking and move on. [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 05:05, 15 December 2017 (UTC)
| |
| − | ::::::::Actually, this "nitpicking" as you call it is exactly the kind of "Learn something new every day" material we need /more/ of on explainxkcd. Do away with people who refuse to actually learn like you (not sure why you're so proud about being wrong but w/e.)
| |
| − | ::::::::This whole comments thread should make it clear that, no, mislabelling it as DOS can not be easily understood. [[Special:Contributions/162.158.126.76|162.158.126.76]] 14:06, 16 March 2018 (UTC)
| |
| − |
| |
| − | : So you use a Windows 10 Dos emulator to run what are effectively dos commands and disparage the guy that uses dos? (I suspect even they are not using a real MSDOS but do use dos commands)
| |
| − | :: No, what I'm saying is that using DOS to run simple command line operations is like having Linux so you can program in C. They have failed to address any actual reason to use DOS over a modern OS. If he was running a potato, or a Pi, or he was running a server, that'd make sense. Or, you know, run a DOS game that literally doesn't work on an NT PC. I totally agree that upgrades without measurable advantages aren't good ideas, but this was a bad example. Though, I also failed to note that the NT Command Line can be mistaken for MS-DOS, and assumed he was using some sort of dual boot. [[Special:Contributions/162.158.2.106|162.158.2.106]] 09:56, 20 September 2017 (UTC)
| |
| − | : I use a calculator app occasionally that has many fewer functions than my first HP35 back in 1973 - the point is it does the job I need, and updating it to 200 scientific functions while entirely possible would not make it "better". Somebody wrote that Windows 10 Dos emulator because for some file and directory manipulations dos does what is needed in the most efficient manner.[[Special:Contributions/162.158.75.166|162.158.75.166]] 02:35, 20 September 2017 (UTC)
| |
| − | :: Wow. No, I don't think ANYBODY is talking about using a DOS emulator! Except the people writing these misguided responses... Just because Microsoft is using the substitute name Command Prompt, and that it isn't the literal Operating System anymore, doesn't mean there's any call for this level of nit picking, to the point of jumping to the weird conclusion that anybody is running commands in an emulator. There's no reason to do this. In my experience, the only reason anyone uses an emlator - generally DOSBox - is to run DOS games, not do anything useful. Calling it DOS is simply simpler that calling it Command Prompt, that's it. There are still no differences in the commands and their use since MS-DOS 6.22, which IIRC is more than can be said about the differences between 6.22 and 6.0. [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 04:32, 22 September 2017 (UTC)
| |
| | | | |
| | Chernobyl and Fukushima were nuclear reactor meltdowns, not nuclear explosions. Also I think three citation needed-jokes in one explanation is too much and not fun anymore. [[Special:Contributions/162.158.238.29|162.158.238.29]] 09:38, 19 September 2017 (UTC) | | Chernobyl and Fukushima were nuclear reactor meltdowns, not nuclear explosions. Also I think three citation needed-jokes in one explanation is too much and not fun anymore. [[Special:Contributions/162.158.238.29|162.158.238.29]] 09:38, 19 September 2017 (UTC) |
| | :I wholeheartedly agree. I've become tired of the general overuse of that joke in explainxkcd. [[Special:Contributions/162.158.79.143|162.158.79.143]] 13:55, 19 September 2017 (UTC) | | :I wholeheartedly agree. I've become tired of the general overuse of that joke in explainxkcd. [[Special:Contributions/162.158.79.143|162.158.79.143]] 13:55, 19 September 2017 (UTC) |
| | :I agree. I am usually a fan of well placed "citation needed" jokes, but not only are these three to rapidly following each other, they also don't fit the usual joke as the statements they acompany can - in my oppinion - be reasonably challenged. Would nuclear fireworks really necasarily cause larger, immediately lethal explosions? Couldn't one build a tiny nuke suitable for a firework? (And with that statement I will probably find myself on a no-fly list)[[Special:Contributions/162.158.89.199|162.158.89.199]] 13:56, 19 September 2017 (UTC) | | :I agree. I am usually a fan of well placed "citation needed" jokes, but not only are these three to rapidly following each other, they also don't fit the usual joke as the statements they acompany can - in my oppinion - be reasonably challenged. Would nuclear fireworks really necasarily cause larger, immediately lethal explosions? Couldn't one build a tiny nuke suitable for a firework? (And with that statement I will probably find myself on a no-fly list)[[Special:Contributions/162.158.89.199|162.158.89.199]] 13:56, 19 September 2017 (UTC) |
| − | ::Heh, I had once theorized building a mock-up of a nuclear explosion audio-visual effects out of conventional materials: some contained explosive for the bang (just a big firecracker), some magnesium mixture for the flash and some hydrocarbons for the raising mushroom-shaped fireball. Then build up a model town and set the whole contraption off while filming it in slow-motion... Never actually followed that idea. Those were happy times, playing with chemistry and making a small flash or bang once in a while. Today, I can't even buy basic reagents...
| |
| | | | |
| | "Real-world fax detractors would rather replace it with other electronic communication systems, not neutronic ones." Wouldn't neuTRONic systems use neuTRONs? Would these be neutrinic, neutrinoic? [[Special:Contributions/162.158.79.143|162.158.79.143]] 13:55, 19 September 2017 (UTC) | | "Real-world fax detractors would rather replace it with other electronic communication systems, not neutronic ones." Wouldn't neuTRONic systems use neuTRONs? Would these be neutrinic, neutrinoic? [[Special:Contributions/162.158.79.143|162.158.79.143]] 13:55, 19 September 2017 (UTC) |
| | | | |
| | "Would nuclear fireworks really necasarily cause larger, immediately lethal explosions?" asked 162.158.89.199. No. Starfish Prime, described in "A Very Scary Light Show: Exploding H-Bombs In Space" at http://www.npr.org/sections/krulwich/2010/07/01/128170775/a-very-scary-light-show-exploding-h-bombs-in-space . | | "Would nuclear fireworks really necasarily cause larger, immediately lethal explosions?" asked 162.158.89.199. No. Starfish Prime, described in "A Very Scary Light Show: Exploding H-Bombs In Space" at http://www.npr.org/sections/krulwich/2010/07/01/128170775/a-very-scary-light-show-exploding-h-bombs-in-space . |
| − |
| |
| − | I think the joke about electrons is based on the speed of electons not the speed of electronic signals. An electronic signal travels much faster than the electrons themselves, which moves more glacially between high and low points (about walking speed).[[Special:Contributions/162.158.114.46|162.158.114.46]] 12:10, 20 September 2017 (UTC)
| |
| − |
| |
| − | An interesting point which Randall may have had in mind: Through at least 2017, the U.S. was still using literal floppy disks (the old 3.5" kind) to run nuclear program software.
| |
| − |
| |
| − | From CNN.com: "According to a new report by the U.S. Government Accountability Office (GAO), which found that the Pentagon was still using 1970s-era computing systems that require eight-inch floppy disks." http://www.cnn.com/2016/05/26/us/pentagon-floppy-disks-nuclear/index.html [[Special:Contributions/162.158.79.65|162.158.79.65]] 18:20, 11 October 2017 (UTC)
| |
| − |
| |
| − | I would argue that one of the main reasons DOS is still found in these sort of production environments, besides the fact that "it works and didn't need replacing", would be simply that DOS is very well-documented from a programming perspective, is EASY to program for, and above all, it allows direct access to hardware without having to do a lot of work. I still use qbasic in real dos to learn and prototype code that will eventually be used in a bare-metal context. Need to write to the serial ports? That's nothing, what if you need to do some very timing-specific things? DOS isn't technically real-time, but that's only because it isn't multitasking. It's almost as close as you can get to it. [[Special:Contributions/172.69.71.142|172.69.71.142]] 15:13, 4 June 2020 (UTC)
| |
| − |
| |
| − | This is a rare case where I wholeheartedly disagree with Mr. Munroe. There's a plenty of so much better supported frameworks than DOS when it comes for basically any place DOS would still manage to do its job these days (usually RTOS of some kind, but sometimes stripped down Linux kernel). To put it into xkcd-style metaphors, it's like opting to use helium instead of hydrogen for party balloons - just overall a better idea that doesn't impact end result all that much. Or, keeping in line with what this strip uses, using modern composition of gunpowder instead of strictly sticking to what ancient China used.
| |
| − |
| |
| − | Now, if this was about trying to shove JS and/or Python everywhere, this would be a very different story... Actually, yeah, that would be [[801: Golden Hammer]]. [[Special:Contributions/172.71.98.57|172.71.98.57]] 14:26, 29 June 2023 (UTC)
| |
