3 ms·
What is the alternative? Make them compile-time options? Expose them to the UI? For all sorts of testing reasons, there has to be a way to disable the JIT. The
by Wowfunhappy 4y ago
What is the alternative? Make them compile-time options? Expose them to the UI?
For all sorts of testing reasons, there has to be a way to disable the JIT. There has to be a way to disable sandboxing. There has to be a way to bypass the GPU acceleration blacklist, and there has to be a way to launch without GPU acceleration on non-blacklisted hardware. Thank god the options exist!
I mostly wish the documentation was better. It would be great if I could filter by platform. And, um, the definitive source probably shouldn't be some guy's personal website.
- zefix 4y agoThe alternative is to not have (most of them) at all. The reality is that 99.5% of users have perhaps 10 or 20 actual usecases/requrements. - You named a few of the most prominent ones. These need to be supported (e.g. with flags) and documented properly. Everything else is excess can be removed. The problem with this is: You need to find out what users want to do. But many software projects are just too lazy and push all the effort downstream.