![]() ![]() It's not actually helping anything, but at least it's not breaking anything. If it's enabled and not breaking things, that's great. The whole situation is straight up flippin' moronic and the only party to blame is Google. There's literally no benefit to keeping it turned on and all sorts of potential benefits to turning it off. It'd still be in the experimental phase and likely causing as many problems as it 'fixes'. That said, I did read that there might be experimental hardware acceleration available for Linux users that also use an AMD GPU. The base software they're using is the problem. Not only is it enabled by default, it breaks some operating systems, 'causing everything up to and including full-system freezes. So, not only does it not work but it's enabled by default. It works just fine in Windows, but Google had 'no plans' to make it work in Linux. There's a HUGE difference between those two things, which seemed to be lost on the person asking the question.Īnyhow, not only is it not working, it exists in the Linux version of the application. It wasn't that it was working on those machines - it's that it wasn't causing any problems on those machines. Brave Browser is a fast, secure, and feature-packed tool, which comes with a trimmed down and crisp interface. So, I shared a link that pointed out that it didn't actually work on any machines and that Google wasn't interested in making it work. (I don't normally have time to visit that site these days.) The person insisted that it worked on other machines. I just had this very conversation on AskUbuntu today. The problem is that Chromium, on which Brave is based, ships with Hardware Acceleration enabled by default. Brave itself is unlikely to be the problem.
0 Comments
Leave a Reply. |