There's now a "Lack of Progress Bar" plugin for Eclipse, that tracks how long developers wait for background jobs to complete. There's an actual use to it! It's meant to focus on how much time the process wastes. As the website says in the "Why use Lopb" section:
Produce ‘hard numbers’ as supporting evidence to convince managers or other non-developers that investments in better/faster development tools and infrastructure have led or will lead to positive ROI in terms of time saved.
Although let's be real, it's also funny.
The name's funny - how do you pronounce it? (I pronounce it "red dwarf," just like I pronounce my last name as "Smif" even though it's spelled "Mayhew")
Plus, I've spent a while wondering if the point of Lopb was to highlight how much time Eclipse spends blocking your productivity - maybe it'd push developers and managers to other IDEs to get away from the Eclipse behavior, or just to get away from the behavior being tracked.
Follow my logic here: Lobp shows 30 minutes a day being tossed down the disposal. Manager John says "You can't be wasting 30 minutes a day! Use that 30 minutes!" So you switch away from Eclipse, still losing the 30 minutes a day, but now it's not being tracked. Everyone wins, except Eclipse.
Of course, that's silly logic too, but then again, you're talking programmer metrics, where we think lines of code is a good metric, too.