Web Compatibility Support • Re: Suggestion for a fallback browser

It is easy to find bad things to say about Ungoogled Chromium, all flaws inherited from its father. Some, such as the poorly designed settings menu which encourages using a search engine(!) to navigate it, have infected other browsers also as they chase current fashions. The worst aspect of Ungoogled Chromium I have yet noticed is not strictly the browser’s own fault, but again, traces to Google proper. If the browser version is too old, it becomes impossible to install extensions from official sources, as I discovered when I first wanted to use Discrub before switching to Waterfox as secondary browser. Possibly, this could be circumnavigated, but I would not know how, and my use case of UC, now my tertiary browser, is so narrow there is no need to bother about it. The future of purportedly extensible, Blink-based browsers years into the Manifest 3 era remains to be seen. One also wonders, as I write this, about the future of web design. Whither is there left to go once almost all sites are the same giant text floating in a JavaScript-generated void? The nicest thing I can say about UC is that it apparently requires less processing power (measured through CPU temperature) than Waterfox for certain JavaScript-based tasks, notably the Mynoise site I recently submitted for diagnosis. Why is this?