Blender 2.8 functioning unusually slow on Surface Laptop 3 (Intel Iris), running low on options

[THugh3]

Blender 2.8, a program I require for work, is functioning unusually slow on new Surface Laptop 3 (16gb ram, i7). I used to use the program on my Surface Pro 4 and it would function just fine. After doing some research, I found this problem affects the entire newest Surface line with Intel Iris graphics, and professionals at Blender Org are attempting a few workarounds, as discussed here: https://developer.blender.org/T70922

and here: https://developer.blender.org/T71287https://devtalk.blender.org/t/blender-2-8-extremely-slow-viewport-with-ice-lake-cpu/9819

According to Jeroen Bakker on the Blender forums, it would be a much more efficient process for Intel to implement a fix in their driver rather than Blender Org attempting the fix, which could take a year.

I also posted on the Microsoft forums to make sure the issue is on everyone's radars: https://answers.microsoft.com/en-us/surface/forum/surflaptop3-surfperf/blender-28-runs-unusually-slow-on-brand-new/46506c8e-945e-46fa-8ba1-efef4b9c543f?messageId=d956ecda-cb58-44bf-b939-bc7ad6dfd189

I was wondering if there is any more action I can take to elevate this issue, as a lot of Blender developers and professionals are running out of options to continue their projects on the Surface line of laptops (and apparently the issue happens on other laptops with Intel Ice Lake 10th gen processors using Intel Iris for graphics processing)

[Gh0stb1t]

"According to Jeroen Bakker on the Blender forums, it would be a much more efficient process for Intel to implement a fix in their driver rather than Blender Org attempting the fix" >> Wrong!!

You have a third party device (Microsoft's tablet) which has its own custom driver, actually they have their custom package of bundled drivers. You need to use ONLY the drivers provided by Microsoft, and if its driver has an issue, you need to narrow down the cause with Microsoft on their device and if they determine the issue is comming from the generic driver, then they (not you) will escalate internally with Intel....

"It looks like if the Blender team were to solve the issue, it would take an estimated year total to work around the issue. Apparently the more feasible option is for Intel to intervene and fix the issue within their driver. " Maybe, but if the issue is due to legacy or poor code development, is the software develper's responsability to work on the solution.