The issue such things face is that they are very difficult to justify. If you say "I am going to improve the efficiency of the rendering process by 30%", no one

The issue such things face is that they are very difficult to justify. If you say "I am going to improve the efficiency of the rendering process by 30%", no one will question what you're doing. The numbers are better than before, so it has clearly improved the software. But if you say "I'm going to implement images in comments", there are suddenly all sorts of questions. Will people use it? What if it degrades experience? What if it contributes to bloat? Etc. If you were to ask which of the features adds more value to the product, the answer is probably the second. But if you look at the feature on its own, it's much harder to justify doing work on the second than doing work on the first because there's no metric you are improving.