Yeah, just stop your X server and run this opaque binary, answer these questions about kernel modules, restart X, and hope your display config isn't completely messed up... super easy!
Note: helper packages (i.e. installer cleanup and kernel mod builder) are in both contrib and main repos, so I highly recommend setting up APT-preferences.
Except that Intel still doesn't make a graphics chip worth anything when it comes to running 3D games like Fortnight. And AMD opensource drivers are far from having nVidia-like feature and capabilitiy parity with their Windwos counterparts. Sadly.
What is missing from AMD's drivers? They are great now IME, I'm using them to play games. (Note I have older GCN hardware - there seem to be more bugs with more recent hardware where they are still making bigger changes)
For a while my employer was buying motherboards with a graphics chip that requires gma500 drivers. Forget which but it was an Atom platform of somewhat recent vintage. gma500 ain't dead yet, sadly
I don't dare update my display drivers unless I have 3 days without a deliverable because of the disaster it usually is.
Usually (yes, more than 50% of the times) it will break my displays (fail to detect both monitors, switch to some weird resolution etc), and always it will break CUDA/CUDNN so I have hours of work making that work again.
I have a completely standard setup: Ubuntu 16.04 LTS, NVidia GPU, Intel CPU.
(I've been using Linux since Slackware 0.9, so yes I do know how to configure things. I'm sick of it not getting better since then).
I suggest you switch to btrfs and use volume snapshots. That way you can take a snapshot just before you do a major upgrade (like a driver update) and if things don't work out you can instantly restore your system so you can keep working.
Historically, drivers were often not available at all, at least not ones that actually exposed the real power of the hardware - and performance is usually lower.
See this set of recent benchmarks for instance, which show Linux performance lagging behind W10 by 15-25%.
These days, the performance diff is mostly from relatively low effort ports. I'm not really complaining about them - they have to earn money.
But in most cases it's not primarily a drivers problem anymore.
//slightly salty