1. 6
  1. 2

    Neat look, though I’m concerned that ctrl+f performance only appears with one hit and that’s a clang warning.

    I like this as an example of the things that engineers care about (“code quality”) but which may be orthogonal to what users care about (performance, having open 100 tabs of social media and porn without draining battery).

    1. 1

      Whatever “code quality” may be in any particular context, if it really is orthogonal to performance and resource management metrics, then I suspect it may be misnamed. Software engineers take care of squishier things like “readability” and “consistency” (and somewhat less squishy things like “test coverage”) in order to enable better quantitative results like faster paint times, fewer memory leaks, or lower overall defect rates. Don’t we?