Google drops another turd in the punchbowl | Hacker News Reader

Google drops another turd in the punchbowl

jwz.org

46 pointsdoty12 comments

so...is it the blogger or the title that makes this not blog spam? it's just a link to jrmuizel's rather level headed blog post from a month ago.

spoiler: http://muizelaar.blogspot.com/2011/04/webp.html

because it's Jamie Zawinski. he is a famous hacker. he wrote XScreenSaver and founded Netscape and Mozilla and dumped a ton of code into XEmacs.

Also runs a night club in SF called DNA Lounge.

And? He's not a codec designer.

JWZ didn't ask anyone to submit his post here, but in the context of HN, this is just linkjacking. Someone should replace it with a link to the real story.

And what?

I was only pointing out the significance of the person as to why he is trending because it sounds if they were not aware of who he was. I'm not giving a position either way as to if this post deserves to be trending or killed as blog spam.

The real story was up trending earlier though.

jwz is pretty well respected, especially in this field. He was one of the original authors of Netscape Navigator. http://en.wikipedia.org/wiki/Jamie_Zawinski

Zawinski would be the first to tell you that he is not pretty well respected in the field of image compression codecs, and he hasn't had anything to do with Mozilla for almost (maybe over?) a decade now.

Disappointed in jwz's choice of punchbowl metaphor. Seriously, why would you call your format Web Pee? Then there's Web 'Emm..', soon no doubt to be followed by Web 'Eh?' (because 'music' also starts with m, guys).

  'Did you know? WebP is pronounced "weppy".'[1]

No. And it isn't.

...It's the little things.

[1] http://code.google.com/speed/webp/

And it's another image format that no one knows how to pronounce. From Google's site: http://code.google.com/speed/webp/ "Did you know? WebP is pronounced "weppy"." Snuh?

I might have the wrong picture of the situation but Mozilla seems to have been reluctant to adding new stuff google and the chrome team are trying to push while the opposite is completely different.

Maybe I'm biased since I think Mozilla should start looking into including NaCL in Firefox. But that's obviously not the only thing they've been blocking, same with Opera.

I dunno, please correct me if my perception is wrong.

Even if that's the case, it doesn't mean Mozilla is wrong and Google is right. Could be quite the opposite.

What has been most disappointing about webM/html5 video, is that Google seems to have halted the roll out on YouTube for several months now.

Google becoming the next .... Symbolics? Too much engineers in power?

Reply on news.ycombinator.com