3 ms·
If Nick is really the one who wrote that piece, it's sad that the Vice President of Firefox doesn't know about image resizing and optimization.
by kdamken 11y ago
If Nick is really the one who wrote that piece, it's sad that the Vice President of Firefox doesn't know about image resizing and optimization.
- callahad 11y agoThat's quite a leap just to get to an ad hominem attack. The way we have WordPress configured should have handled this automagically. I'll look into why it didn't.
- kdamken 11y agoI wasn't trying to personally attack the guy, it was just surprising that an article by one of the heads of a major tech company wouldn't have something basic like that taken care of. I'd recommend the tinypng plugin (https://wordpress.org/plugins/tinypng-for-wp/ https://wordpress.org/plugins/tinypng-for-wp/), which will do the optimization (though not resizing) automatically for you. Edit - More downvotes, someone is having a tough morning.
- x1024 11y agoI don't know about "ad hominem", but you are demonstrating technical incompetence while attempting to pitch a technical product. That's a big, biiiig red flag. Yes, "it's a very minor thing", but then again it's maybe the only way you can reasonably screw up a blog post, and you did it.
- fareesh 11y agoTheir content management system should ideally do it for them, minor point but yeah.
- billyhoffman 11y agoYes, CMS should do lossless optimizations no question. The problem here is that this is a photographic image, saved as a PNG, when it really should be a JPEG. Converting to JPEG is a lossy optimization, in addition to offering different features. It's risky to have a general "convert PNGs to JPEG" or even "convert all non-transparent PNGs to JPEG" optimization rules built into your build process or as a CMS plugin
- dang 11y agoWe detached this subthread from https://news.ycombinator.com/item?id=10696460 https://news.ycombinator.com/item?id=10696460 and marked it off-topic.