Considering the amount of legacy soft- and hardware the drivers have to interact with as well as all the fixes specific Programms need, its a complete nightmare to write these drivers. Especially since they pivoted from raw processing power to a mich more software supported system.
What I can’t excuse is the abysmal amount of quality control the seem to be doing.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
No game suggestions, friend requests, surveys, or begging.
No Let’s Plays, streams, highlight reels/montages, random videos or shorts.
No off-topic posts/comments, within reason.
Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
How fucking hard can it be to write a functional driver for the device you built yourself?
Considering the amount of legacy soft- and hardware the drivers have to interact with as well as all the fixes specific Programms need, its a complete nightmare to write these drivers. Especially since they pivoted from raw processing power to a mich more software supported system.
What I can’t excuse is the abysmal amount of quality control the seem to be doing.
Like, very very very hard? The kind of hard that can’t be vive coded?
If I’m not mistaken most of the driver is fixes for games doing weird shit with graphics api.