News for hackers. Stuff that matters.
Re:Favicon bug by Someone1234 on Monday June 15, 2015 @01:39PM (#9720809)
Just doing some quick back of napkin maths, even assuming Apple's 128x128 app icons, and 48 bit colors (32 is more typical), we're still talking about a sub-100 kb max for a favicon.

So if Chrome set it even at 20 Mb that would still be orders of magnitude more than any favicon should be for at least the next five or so years (even assuming 256x256 became common for app icons).

Re:Favicon bug by vacri on Monday June 15, 2015 @05:53PM (#9722357)
"The most memory anyone needs is 640k"...
Re:Favicon bug by ahoge on Monday June 15, 2015 @06:19PM (#9722499)
Hard limits aren't much of an issue if updates are rolled out ever 6 weeks.
Re:Favicon bug by jfoster on Tuesday June 16, 2015 @02:25AM (#9724105)
That was said with a wide open scope. Bill was wrong because he hadn't imagined all the things people might do with PCs. In this discussion, the scope is very limited; favicons.
Re:Favicon bug by miahi on Monday June 15, 2015 @01:48PM (#9720852)
You can have animated favicons.
Re:Favicon bug by tomswartz07 on Monday June 15, 2015 @01:50PM (#9720868)
Even still, the animated favicons would be low framerate and fairly low resolution.

I don't think we're ready for 60 FPS .gifv favicons just yet. :)

Re:Favicon bug by daurnimator on Monday June 15, 2015 @07:20PM (#9722818)
Re:Favicon bug by logicallee on Monday June 15, 2015 @02:40PM (#9721152)
ten gigabytes is a helluva favicon animation... I wonder if it would be measured in hours, days, or weeks...
Re:Favicon bug by Johnny_Brahms on Tuesday June 16, 2015 @03:20AM (#9724233)
Let's go ahead and implement webm favicons. Months of pleasure from every single website visit!