4 ms·
> Ten years ago, using a six year old machine meant you wouldn't have a snowball's chance in hell of running new software [...] Do you have some evidence for t
by runeks 9y ago
> Ten years ago, using a six year old machine meant you wouldn't have a snowball's chance in hell of running new software [...]
Do you have some evidence for this claim? I'm not saying I disagree -- indeed, I suspect it might be true -- but I'd appreciate some evidence to back it up.
- megaman22 9y agoTwo that come to mind are Windows Vista upgrades, where many XP-capable machines were just not powerful enough to handle it. The other would be video games, which were constantly pushing the envelope. Consoles may have a lot to do with the stagnation in the latter case, however.
- Brockenstein 9y agoRight. I bought a Pentium 3 800/GeForce 2 GTS in the summer of 2000. And by 2003 Homeworld 2 and Knights of the Old Republic had a Pentium 3 833mhz and a Pentium 3 1ghz respectively.
- ptero 9y agoI do not have statistically significant evidence, but as another data point I have the same experience: both my home and work machines are 7-8 years old and work just fine (30" monitors, decent performance with numpy, MATLAB, compiling, perfectly fine graphics, etc.). But around 2000 I remember always carefully looking at the system requirements section of games to check which of those would work on my 2-3 year old computer and for which my machine is too old -- and find a significant rejection rate (25-50%).
- electrichead 9y agoI don't know if that needs any evidence of the person was simply around back then. Basically this is saying that 2001 hardware wouldn't be able to run the new software in 2007, which at least to my recollection, is absolutely true. Not only is there 32bit vs 64bit, we also started to see more cores rather than the standard single core in 2001
- ghostbrainalpha 9y agoI agree with you that this claim doesn't need evidence, but for anyone interested. Starcraft 2 came out in 2007. These are the original system requirements. https://www.lifewire.com/starcraft-ii-wings-of-liberty-requirements-813007 https://www.lifewire.com/starcraft-ii-wings-of-liberty-requi... I remember receiving the game as a gift and having to tell my grandma that my single core PC wouldn't be able to play it. I think my PC was only 3 years old at the time, not even 6.
- Brockenstein 9y agoI think you're miss-remembering. Starcraft 2 Wings of Liberty was released in 2010. I played it on release on my Core 2 Quad/GeForce 8800 GTS machine that I built in 2009. Blizzard announced they were making SC2 in 2007. https://en.wikipedia.org/wiki/StarCraft_II:_Wings_of_Liberty#Development https://en.wikipedia.org/wiki/StarCraft_II:_Wings_of_Liberty... there wasn't even a closed beta until early 2010. Regardless, the minimum requirements you posted are single core CPU's.
- deathanatos 9y agoIt's a bit further apart than the mentioned dates, but I bought two machines: * 1998: 32-bit, 500 MHz, single core, 128MiB of RAM IIRC (we later upgraded it to ~500 MiB). 7 GB of disk. * 2007: 64-bit, ~2.5 MHz, dual core, 4, later 8 GiB of RAM. Hundreds of GB of disk. There's essentially an order of magnitude improvement…
- rangibaby 9y agoVista / 7 needed 1GB of RAM to run correctly. The systems from 2000 that I was familiar with had 512MB of less.
- Brockenstein 9y agoIn 2000 128/256 would have been common on new midrange systems. 512MB would have been high end or had RAM added after the fact as an upgrade.
- wil421 9y agoAnyone using a computer back then ran into the same problems. The upgrade from Pentium to Core2Duo to the iX series was very noticeable. Not to mention the 32 bit to 64 bit transition that allowed us to use more RAM in Windows. IMHO, the upgrade from HDD to SSD was the most noticeable speed jump.
- Brockenstein 9y agoTen years ago, in 2007, using a machine from 2001. Probably a second generation Pentium 4 (https://www.intel.com/pressroom/kits/quickrefyr.htm#2001 https://www.intel.com/pressroom/kits/quickrefyr.htm#2001) or Athlon XP, with less than a gig of RAM or if you had upgraded it by 2007, probably 2 gigs or less. A Yeah, that would be pretty crummy in 2007 even if you'd bought a high end system in 2001. If it was entry level, forget it. I mean you'd still be able to compute things in 2007, but the overall experience would be sub-par. And a lot of things would run technically, but it would be painful enough you wouldn't even want to bother. My take on it is that multi-core CPU's caused the amount of computing power available on even budget systems to grow exponentially faster than software demands for that power. Not only is it more cores, but the power of a single core has also increased steadily. And the first Core Duo's were easily faster per core than the previous fastest single core Pentiums on top of having two cores. More power, better multi-tasking, it's a no brainer. The amount of computing power has increased much faster while software demands just haven't kept pace, and most software just doesn't require 3.5ghz and four cores for an optimal experience. The result is five, six, seven year old PC's are still perfectly serviceable. The same just generally wasn't true in the era of single core PC's.
- pjc50 9y agoRecently I fished out my Toshiba Libretto 30, which I bought in 1998. It had just about enough processing power to play MP3s using the Fraunhofer codec, but not run WinAmp. Over the next couple of years the use of MP3 exploded: Napster, the iPod, iTunes. The boundary for "can this system decode mp3 in real time" was somewhere around the late 90s. Now of course it's not an issue on any device.
- gilbetron 9y agoLike others have said, it is something that was extremely apparent to anyone around 10+ years ago that made use of computers. Back then, a computer was simply 2x as fast every 18 months. If you had a game that ran at 30fps, and you bought a new computer 18 months later, it would run at 60fps. Likewise, a new game would run at half speed on a computer that was 18 months old. While there are limits, the scaling largely held up over time. A game that ran at 15 fps (60 fps wasn't really a thing back then, usually you hit 15-30 fps) would be 32x faster 7.5 years later. Ditto with most software. The vast majority of speedup, from a processing standpoint, these days is all from increased parallelism (via more cores, or more SIMD-like instructions in the core), and because of Amdahl's "law", it can be very difficult to see benefits from increased parallelism. We're still seeing Moore's law for drive space, RAM, and somewhat bus speeds, and that's also where you get a lot more speedup.
- wott 9y agoAgreeing with the rest but not the end. > We're still seeing Moore's law for drive space, Not really. 2Tb became a standard a long time ago, and it didn't change afterwards. Speed did not improve much either, especially latency (it cannot really improve), except by switching to SSDs, but then you lose capacity, so it is not a continuous improvement. > RAM, and somewhat bus speeds, and that's also where you get a lot more speedup. SDRAM is slow as molasses, as far as latency is concerned (the "Random Access" in R.A.M.). The improvements have been incredibly small in this domain. DDR4 access times are slower than SRAM access time from perhaps 20 years ago. It has however much larger capacity and larger throughput, indeed. > and somewhat bus speeds, and that's also where you get a lot more speedup. Same problem with buses, their frequency raised a lot, but that happened with switching from parallel to serial buses, leading to a lot of latency (and overload), not only on the bus itself because of the protocol, but also before and after because you need to serialise and then deserialise the data for you need it in a parallel form anyway. For example, the first SATA, despite its impressive frequency of 1.5 GHz, did not do better than the good old IDE/PATA with the latest UDMA. Same for PCI Express, it showed 2.5 GHz frequency, but its performance was not better than AGP or top PCI with their < 100 Mhz frequencies. Then to improve the throughput you had to add multiple lines of serial buses, which again add some need for synchronisation and thus extra latency.