This, plus proliferation of antialased rendering offsets advancements in CPU power - to the point that navigating source code in QtCreator on my Linux box is not that smooth as I'd like it to be.
That almost certainly has more to do with either display sync issues (which sadly aren't uncommon on a composited X desktop especially with non-free drivers) or the various services of the IDE. Anti-aliased font and line drawing aren't that demanding to begin with, and can be GPU-accelerated with pretty much any hardware you might have picked up within the last five years or so.
Quote: "Adopting a new image format in Web browsers is a big decision. Once a format becomes a part of the Web, it will have to be supported in perpetuityâ"adding overhead to the browserâ"even if it largely fizzles and only gains a small niche following."
It's akin to if Web browsers were required to support failed formats like ANIM or HAM or IFF.
In practice that doesn't seem to be the case; see, for instance, the state of MNG support in Gecko-based browsers. On the other hand, the adoption of APNG in Firefox has been a catalyst for its spread into wider use.
The life of a repo man is always intense.