Re: Samsung will probably make the same mistake Intel and AMD made
I will admit that the three times I bought an Nvidia GPU (2007, 2012-ish, 2016-ish) quality of drivers (esp. on GNU/Linux) was my main concern. However, right now the big advantage Nvidia has for all non-home/non-mobile workloads is CUDA (not necessarily because it's better than OpenCL et al, but due to being first and therefore having lots more compatible software). On the home PC market, Nvidia (and AMD) have the advantage of having humongous piles of workarounds for specific games (which Intel should've also had from their iGPUs...), and AMD currently also have decent drivers. Still, Intel launching a GPU with essentially no driver support for DirectX < 12[1] was one of the decisions of all time. Props to Nvidia for having the best money-no-object hardware of the current generation (RTX 40X0), and likely the next one too.
IFF Samsung is throwing their hat on designing/building their own GPUs for the mobile market, driver support should be easier than on PC. The mobile GPU market is already much more heterogeneous than PC GPUs, and the chances of Google/Phone Manufacturers doing patch releases of their GFX stack to support badly coded games is much lower.
PD: From hearsay (and some personal experience, esp. near 2007), ATI/AMD drivers varied between almost tolerable (mostly on Windows, usually near or after the cards went EOL) to unmitigated disasters (esp. on GNU/Linux). It only got better around late 2010s, to where all my daily PCs sport integrated or external AMD GPUs and I couldn't be happier about them. (The only remaining issue I personally had -- also with Nvidia but not with Intel iGPUs -- was hangs after kexec, but it seems to be finally fixed).
[1]: Intel straight up use vkd3d/dxvk (as seen in Wine and Proton) for DirectX 9/10/11 support.