I'm not convinced [1] [2].
Oh, and the sales pitch for WebKit is pretty weird, given that Chrome forked WebKit into Blink, and the whole thing is built on NaCl, a technology that WebKit is not going to integrate.
Are you seriously implying that pocketsphinx in JS will do anything close to the level of voice recognition necessary to recognize pretty much anyone's voice, sight unseen? I mean, really? You kinda need to train the hell out of that thing to get it to recognize the difference between "merry christmas" and "happy hanukah", and even then, it will only really work for one person.
> You kinda need to train the hell out of that thing to get it to recognize the difference between "merry christmas" and "happy hanukah", and even then, it will only really work for one person.
So compile an engine you like better.
You claimed that voice recognition and synthesis "could not possibly be done in any other browser". As in, it's impossible. The fact is that you can do it by just compiling your favorite engine to asm.js, and people have done just that with several of them. So your sales pitch for Chrome is wrong.
If you want to say that it's easier in Chrome because of the Web Speech API, that's fine. But impossible in other browsers? I don't believe it.
(Hi Mom!)
About the "Why chrome?" page. I needed to put something there to explain why you need to use Chrome to get any use out of the site. I realize anything that I put there will only wind up as flame bait, so I tried to make it as "politically acceptable" as possible. The bottom line is that I couldn't care less about those political arguments. To me, the web will always be more about technical merit than anything else. Back in the "bad old days" of the original browser wars, Mozilla was at the forefront of pushing the technical boundaries of the web. Not so much anymore. Such is life.
But don't let that stop anyone from engaging in an old-fashioned flame fest. Anything that gets this to the front page of HN is a-okay with me :)
They tried sending an email asking people to repost. Now they adjust the time stamp and apply a small (1 extra point?) bonus.
KHTML?
I understand NaCl is a way to execute x86 binary code inside a Web browser.
I also understand NaCl is not enabled by default.
I can't see anything anywhere on this page that eg fires up DOSBox.
I also can't see anything giving me errors saying "NaCl is not enabled!"; I'm running the stable build, which doesn't enable it, and I've had no reason to change that.
This looks like yet another reimplementation of a "web-based desktop".
I thought we were past this sort of thing, no?
