One thing that bothers me in today's computers, is that pretty much everyone is sold on to object-oriented programming, but we're still doing it half-heartedly at best.
First peeve, of course, is that most projects are still using C, a terrible language which isn't really good at anything. They happily rant on about its "low-levelness" and speed, and use that as an excuse not to design a proper language that has these same properties. But this doesn't really matter for the topic at hand.
What really bugs me is not our languages, but our systems. 30 years later, we're stuck in systems based on the assumptions, metaphors and paradigms of the multics/unix family.
We're still organizing our data in artificially-hierarchical trees, with opaque byte-streams as leaves; consequently, we're still wasting hundreds of hours per project, figuring out ways to efficiently represent our data as byte-streams.
We're still running huge, monolithic "processes", with big startup costs, and which we have to keep running (wasting system resources) as long as we want to use certain features. (To be fair, this is not a multics/unix thing; unix processes were supposed to do atomic operations and be lightweight.)
I'm tired of the "application". I'd rather have classes or objects. I'd rather not have "processes" hanging on, "waiting"; instead, the "normal" state of the system is to have no "processes", or a very small number of them, and lightweight, short-lived "processes" are fired up to respond to events (methods?).
Another thing that bugs me is that some people write "oop" "apps" in C, others in C++, others in java, others in C#, others in python, and these "apps" are "oop" only internally; they interact with each other and with the user in a completely non-oop way. One can't call methods on (or send messages to) another. Things like corba, .net, and vos, come to fill that void, but still in a somewhat limited way.
This is all horribly inefficient, because we have to run loops around ourselves, we have to spend a good deal of time writing these "adapters" so that our reasonably modern applications can communicate using the paleozoic interfaces we insist on sticking to. It's like living on a world where everybody has a skycar, but we are forbidden by law to take them off the ground. I feel stuck in traffic.