I'm not sure why you think modern software is slow, but it is definitely not those two things, unless they are implemented EXTREMELY naively, which is far, far less common than one would think.
> I'm not sure why you think modern software is slow, but it is definitely not those two things
I think modern software is slow because it's slow (despite having vastly more powerful computers), those 2 things along with the language apps written in are the major technical differences between old software and modern software. If theory doesn't match reality then the theory must be wrong.
This app starts is more responsive than my windows start menu.
Yes, the application starts very quickly and feels instant (which is how ALL software should be, dammit.)
I GUARANTEE you that any lack of multi-threading or hardware acceleration is not the cause for the speed, but rather the simplicity of the application. It's as complex as it needs to be to perform its job, and not more.
Today's unfortunate software development practices stack layer upon layer of abstraction on top of the CPU; far more than was the case when this application was written. As such, more modern applications are bogged down with the weight of all of this stuff.
Developers today have forgotten that "mo' code means mo' problems" and are quite happy to reference any stupid library they come across in order to make things feel simpler. What they've actually done is make things far more complex, and complexity is the undying, always victorious, enemy of performance.
I don't like that modern applications are slow, either. They aren't slow because of multi-threading and hardware acceleration, I promise. They're slow because of piles of stupid decisions on how software should be built.
Hardware acceleration is usually good.
I'm not sure why you think modern software is slow, but it is definitely not those two things, unless they are implemented EXTREMELY naively, which is far, far less common than one would think.