Hi Nick! - we may see TC from a different angle, but I believe for the most part we are on the same page!
But we can't stop progress. If you were to put your laptop up for sale today, I may not feel it's worth more than only $40.
But don't feel bad - back in the day, corporations paid millions of dollars for a large timesharing system, and within 4 years it was totally obsolete. Minicomputers and all that. Which also had a real-term lifespan of only a few years at most unless you handed them off to uni's to run basic with.
So these days, with near disposable super/mini personal computers at our disposal, with crazy high clock speeds, ram and storage ...
What used to be tight, efficient, and elegant code partly mandated by limited resources, could today be seen not from a technical viewpoint, but a transition from science to art!
That is, with unlimited disposable computer resources, one can simply make it a large unmaintainable mess, OR still create tight, efficient, and elegant code simply as a personal choice! Almost an artistic choice, be it the code itself, or the group of like-minded people creating it.
It's a luxury. Which leads to possibly making decisions not based solely on hardware limitations, but "What's the most *elegant* way to handle an issue?" be it code or group involvement. Perhaps some things could be made a *tad* larger if it doesn't impose a hardship or be harder to digest - but always keeping an eye for creeping-featurism.
We've got that luxury now as users or developers to find that "balance" between minimalism and bloat. Extremes on either side are
inelegant.