No problem. Well, ehrm, maybe …
I like it clean and well arranged.
I don’t like proprietary formats like GIF or – even worse – ICO.
I use a PNG for my favicon.
I don’t want to have to create/convert a GIF and ICO variant of my PNG favicon.
Looking for a favicon.ico in site root is bullshit.
1.) There is a standardized way of referring to the favicon of the site with the meta element - so you can place it where-ever you like.
2.) ICO is a Microsoft format. No good support with free software.
I don’t want any bot/agent looking for /favicon.ico to find one.
I don’t want it to find an empty favicon.ico.
I don’t want it to find the favicon.ico as a copy of my real favicon.png.
I don’t want it to get redirected to /img/favicon.png or so.
I just want them to find NO favicon.
They shall use the correct way of parsing the meta element. If you keep them giving what they want, they won’t change.
And maybe there might be problems with some multi-site functions of a CMS. When you set a favicon for each subsite with the correct way (meta element), there is still this dreamhost-created favicon.[ico|gif] in site root. So some agents, which might look for BOTH methods (favicon.ico in site root -or- favicon referred to in meta element) might try the favicon.ico variant first and find this empty favicon. I couldn’t even fill this favicon.ico with my real favicon, because I need several different favicons (because of multi-site).