If you can honestly look at a modern PC motherboard and associated components and not see 2 decades worth of accumulated cleverness in the component parts and their interconnections then there's no point in me even trying to point any out. You simply don't, or won't appreciate it. Which is your prerogative.
That's not an answer to the question, that's you telling me that I don't want an answer to the question, and
I'll be the decider of my own motivations, thank you. If I wasn't interested in hearing your view on it, I certainly wouldn't have wasted my time asking.
So I'm very curious of what they make of Wayland as the only resource-hungry aspect of Linux is the x-windows system.
Wayland has some good ideas at the core, and yes, XWindows is
ripe for replacement. Problem is, as far as I've read it sounds like they're betting everything on GPU acceleration, which is only good if you have
working GPU acceleration. In Linux, that depends largely on what exact core of whose basic architecture your GPU uses, and the open-source driver projects for even the big names in video cards are pretty scattershot in their support.
Wayland claims that'll be taken care of by a software fallback layer. Ideally that would mean no worse performance than a non-compositing window manager, which would be pretty fine. Unfortunately, what
they're planning to do is run the compositing window manager
through the Mesa software renderer. Which, if you've ever used it for anything more complex than a spinning-teapot demo, is a sluggish agony. So if your laptop has an unsupported chipset, the question will be whether or not the pain of maintaining and using X is worse than the pain of using Wayland on a software emulation of hardware acceleration.