I think it’s rather — just as Moore’s Law — a psychological phenomenon rather than a mathematical one. There’s just so many seconds we’re willing to wait and at one point, we don’t even care. Also the Internet hardened us for long wait/download times.
And that view isn't a psychological rewrite of the past. I regularly game on systems from both the 90s and modern day, and the load times for modern games are usually much worse than the CD games of old. The funny thing is that people would complain like crazy about CD load times back then, even citing it as a reason why CDs could never become mainstream.
And yet, here we are present day with obscenely shitty load times for most software.
I think the one area that has improved dramatically has been video streaming though. Real Player and the like were terrible even for their time.
Uhhhh, well I don't tend to wait 3-5 minutes for a single .jpeg to load on a website any more. I can stream a hq video in real time over the internet, whereas downloading a single 30MB realmedia video so pixelated you could barely see what was on the screen would take an hour or more to download. A 3MB mp3 would take 5-10 minutes. There have been massive speed increases in web surfing for sure. I don't understand how anyone that used the web back then could think otherwise.
As for software load speed, the amount of data being loaded off a CD for a 2d or older 3d game is magnitudes smaller than the data being loaded from modern games. How many gigabytes of high res textures did those old games used to load? How many uncompressed HQ sound effects and music tracks? I remember installing multi-CD games and waiting and waiting,.then swapping the disc, then waiting then waiting, then back to disc one, more waiting, now disc 3.
I'm not saying those things are better, but there's no way in hell my old 486 could have loaded multiple gigabytes of data at the same speed my laptop or even my phone now does.
That was not true on 56k in the late 90s. On a baud modem in 93, sure, but I wasn't talking about that.
As for software load speed, the amount of data being loaded off a CD for a 2d or older 3d game is magnitudes smaller than the data being loaded from modern games.
Irrelevant. The amount of multimedia on a CD was vastly more than the main memory available at the time. Plus you didn't have multi cores, SSD storage (or any HD) etc.
No one optimizes anymore, and it shows.
>Irrelevant. The amount of multimedia on a CD was vastly more than the main memory available at the time.
I don't follow. It's not like all available memory is ever used to load things from storage. All I know is, I can copy an 8GB DVD on my current computer with 6GB of RAM faster than I could have copied a 756MB CD with around 500MB of RAM.
I do agree nothing is optimized as well, but that's some hard nostalgia goggles talking there.
We should be seeing much better load times than we are given current hardware, not incrementally better or even worse. Which is the reality, since no one optimizes anymore.
But I was there in the 90s, too.
Sure, the load times on an NES are better than, say Fallout 4, but I remember starting up Ultima 8 for the first time and that was some sincere amount of wait.
I think that things are much better now, at least in the few games I've played in the last couple of years (Bioshock, Detroit: Become Human, Fallout 4, Red Dead II). The content is way more developed, and instead of loading a pile of floppies, I just wait for it to DL what it has to do. Granted that takes a while, but at least I don't have to hand feed it.
Ahhhh ok you got me there. Floppies were terrible, and playing games on a low end DOS machine was terribly slow. I have played modern games that were about as frustrating though, but only if they're completely broken.
I was referring to game consoles though. Load times on Sega CD on 3DO were terrible for the time and turned off a lot of consumers back then (though not the only reason those platforms failed, they were just the slowest of the bunch). But the load times in modern games is typically far worse than those systems ever saw.
I switch between modern and retro era systems frequently, and I find modern load times embarrassing given what people were up in arms about back then.
Jonathon Blow tends to agree with me, FWIW. Check out some of his talks on the lack of optimization in modern software if you have the chance. Modern software should be a lot faster than it is given the hardware capabilities, according to him too.
I think nowadays, these online arena games take forever to load. Back in the 90s it was all about loading and performance. Quite the shift in gamer expectations.
I think one of the first actually useful programs I've written in my life was a conditional in the autoexec.bat script that let me choose different memory configurations. What fun times :D
I personally only game in short bursts so it's not a big deal to me to let the machine spend a whole damn day downloading fallout over a 10Mb DSL line.
I mean, that was better than spending the whole night DLing Commander Keen.
My view is that there's a certain amount of time that I'm willing to wait for certain interactions, and that's pretty consistent regardless of the tech stack. So if I have to wait a bit, I do.
I'm far less patient with things like keyboard shortcuts, UX interactions... but I feel like a lot of those really have gotten way, way better (like, no more floppies). Perforamnce is just one aspect of UX, and while you're right that it could obviously be better, there are so many other parts that are so much better (and performance really isn't worse that it was when I was playing Police Quest V).
Lately I've been making something of a hobby of replacing big scale-out Apache Spark ETL jobs with stuff that was hand-coded to use something other than Spark. Generally I'm finding that, with a little care, I can get a lot of these jobs done in less time on a single machine than I can running it on the Spark cluster. (Using code that's easier to reason about, too.) And even when I can't, I'm not sure it's enough slower to warrant the use of the cluster, on the principle that using half a rack worth of compute resources to get the job done in 45 minutes when you could do it in 60 on a single box isn't really a good tradeoff.
All that long-windedness by way of saying, these big data tools are kind of slow and bloated. They're slow and bloated precisely because they have more features. All the extra work they need to do to achieve reliability when you're scaling out has a cost. But that doesn't necessarily mean that the cost is justifiable.
A box truck is more capable for running errands than my Kia Soul, because I can fit half the grocery store in it. But I think we'd all agree that it would be an obscene waste of money to default to using a box truck to buy groceries and make Ikea runs, and justify that decision by pointing out that some small fraction of the time I'll need to transport more stuff than will fit in a Kia Soul, and it's better to standardize on a single model of car. In a computing setting, though, we do that sort of thing all the time.
We've started to come around with languages like Rust, but a lot of engineers have (in my opinion rightly) come to the conclusion that it's better to abuse the faster speed of computers to have a higher assurance of the software being correct. Could I conceivably get better performance if I wrote something in C and wrote a custom allocator? Maybe, but I'd probably make a mistake, and my GC'd language is fast enough for most of what I do.
Much as I think Java is a garbage language, there's no doubt that, by default, it's safer than a program written in C. It also typically is bigger, requiring a bit more RAM and resources.
Then C++ started to gain market share on OS/2, Windows, BeOS, Epoch, macOS, Newton as the way to write UIs, even if their kernels and low level APIs were written in C, or C with C++ compiler style.
All C++ libraries bundled with compilers, provided strings and vector types with bounds checking.
It was the rise of C's adoption thanks to FOSS that brought the unsafety wrath upon us.
That's why Windows is the size it is nowadays... it's optimized for delivering the same user experience on all hardware, compatibility, language flexibility, manageability and user friendliness (don't laugh) instead of performance. It essentially performs the same function that Windows 3.1 did, but it does it on a far greater variety of hardware running a far larger assortment of software.
It's bigger and slower than it could be, but there are always trade-offs, and Microsoft hasn't really had any competition in operating systems for decades... Linux and variants have their place, but it's not on the desktop for most people, at least at the moment.
However, taking your example, the filters can't really be optimized because they're applications run on top of a bloated operating system which isn't optimized for the reasons I mentioned.
Writing a highly optimized program to run directly on the hardware of a given machine would speed up filters tremendously but also be a trade-off in terms of manageability.
Here's an example. In the mid to late 90s, gamers would complain a lot about load times for CD ROM games. For some gamers, the load times were a deal breaker. This was one reason Nintendo could get away with using cartridges on the N64.
Fast forward to the present, and load times for many mainstream games is FAR worse than the 1-2x speed CD based consoles of the 90s. And a lot of this is due to sloppy, unoptimized code, e.g. loading assets. And yet no one bats an eye.
Another example is the web. There are so many garbage, unoptimized sites that load on my smartphone as if I were on dial up (I'm looking at you, Gawker). Yes, those pages contain a lot more multimedia content nowadays, but they still load at the same rate as a typical page in the 90s would have on dial up.
And with Moore's Law now ending (ended?), optimization may come back in vogue.
As for load times today, most modern games are implemented as scripts and assets for one of the big engines, usually Unreal or Unity. It's hard enough to manage all the assets that go into a modern game; an optimized loader would just make wrangling them all even more difficult.
Yes, I realize that. But the point was that poor decision was not enough to kill it, and the N64 was still a commercial success. A lot of gamers even preferred cartridges back then because of they didn't require load time.
As for load times today, most modern games are implemented as scripts and assets for one of the big engines, usually Unreal or Unity. It's hard enough to manage all the assets that go into a modern game; an optimized loader would just make wrangling them all even more difficult.
That's not a real reason to not optimize.