5 ms·

Yeah, trying to fix this would be a clear example of "premature optimization". Youtube isn't some low data use application, where undisplayed HTML is a signifi

Yeah, trying to fix this would be a clear example of "premature optimization". Youtube isn't some low data use application, where undisplayed HTML is a significant source of wasted capacity. Even if it were, the right answer would probably be some layer between HTML generation and delivery that gets rid of cruft. Software engineers are really expensive.

agumonkey 6y ago
and this is how you get a vestigial tail
- cortesoft 6y ago
  Is that bad?
  - maerF0x0 6y ago
    it is when it becomes the source of bugs. To keep the analogy rolling perhaps some had phantom pains in their vestigal tails until their brains adapted to the missing item?
  - agumonkey 6y ago
    it was non judgemental
foobarian 6y ago
So far the discussion was about the title text being replicated inside the HTML, presumably coming down in a single request. But, I would also not be surprised if redundant service calls occurred to fetch the data; especially when different teams are involved in maintaining a page coupling their designs adds a lot of burden that is probably more costly than just living with a little redundancy.