From what I understand about it, it is a linux kernel + driver issue. I do not know if this means it is the manufacturer of the chromebook's "fault", or google's "fault" for not supporting these things. E.g. does the manufacturer need to do a new build for their hardware? I don't know.
The chromebooks do update themselves all the time but I gues there is some more fundamental stuff that requires more low-level changes.
https://arstechnica.com/gadgets/2019/11/google-outlines-plan...
As an example, Vulkan was added in Android 7 as optional API, the adoption was so low, with so many buggy drivers that as of Android 10 it became a compulsory API.
On Android everything that Google leaves the OEMs free reign hardly gets done.
1 - https://support.google.com/chrome/a/answer/6220366?hl=en
Microsoft just ended support for Windows 7 - released July 2009 - yesterday. It’s currently running on my old 2006 era Mac Mini that my mom is using.
I also have a 2009 Core 2 Duo laptop that until early last year was my Plex Server. It is running a still supported Windows 10.
Both Microsoft and Asus keep having updates for it.
Google just needs to actually care.
In fact, Android since project Treble has a driver model similar to Windows.
Linux drivers are considered legacy on Android.
Likewise they could have contracts in place that would force their suppliers to provide updates for X years.
Google always kills their products unexpected for all, don't matter which audience you are.
I guess there would be 0 hardware manufacturers left to choose from then.
Maybe I overestimated how much leverage Google has then :/
My dell xps 13" touchpad drivers didn't work from synaptics, it had to be from dell. Something else needed realtek driver direct from their website, windows updates version were broken.