Comment by tossandthrow
9 hours ago
> but decades of feedback, tuning and fixing
On the contrary, this is likely the reason why we can disrupt these large players.
Experience from 2005 just don't hold that much value in 2025 in tech.
9 hours ago
> but decades of feedback, tuning and fixing
On the contrary, this is likely the reason why we can disrupt these large players.
Experience from 2005 just don't hold that much value in 2025 in tech.
It absolutely does. I cannot believe I am reading this on HN... Do you think the idea of a pointer changed? That you need locks when accessing variables when doing multithreading? That principles like "Be conservative in what you send, and liberal in what you accept" have changed? In fact, almost nothing changed from 2005 to now in any conceptual form.
The short answer is that these things don't really exist anymore for most (business) applications when you stopped writing it in C.
So the things you mention indeed is experience you need to get rid of as you move to other software stacks and other technologies.
Software was never coded in a big-bang one shot fashion. It evolves through years of interacting with the field. That evolution takes almost same time with AI or not. Remember a version release has many tasks that need to go at human speed.
On that we agree.
But taking out features are difficult - even when they have near to zero value.
Why it sometimes make sense for new players to enter the market and start over - without the legacy.
This is indeed one of the value propositions in the startup I work in.
> Experience from 2005 just don't hold that much value in 2025 in tech
That would be why a significant portion of the world's critical systems still run on Windows XP, eh?
No, that is likely because there is no economic benefit to do anything about it - definitely not UX concerns.