Live data from Hacker News

I made a talking emoji using regular emojis and JavaScript

hackernoon.com

61–63 of 63 posts

Re: I made a talking emoji using regular emojis and JavaScript

#61

Earlier quoted context omitted.

British English has at least two pronunciations of money that I know of, /mʌni/ and /mʊni/

The former is the most common way for Americans to pronounce it, and matches the mouth shape of ah, and the latter, while not common in the US, also matches the ah mouth shape. I really don't know how yesenadam is pronouncing it such that his mouth doesn't take the ah shape.

Ohhh. I'm sorry everyone. Yes, you're right of course. It didn't occur to me until I tried it that the bu- in bun is bahhh. Goes back to drawing board

Re: I made a talking emoji using regular emojis and JavaScript

#62

Earlier quoted context omitted.

"Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize."

..which would be, what?

The fact that phoneme letters should have been used instead of alphabet letters in order to decide what mouth shape the icons should have.

Re: I made a talking emoji using regular emojis and JavaScript

#63

> an emoji, in reality, looks like this: “\xF0\x9F\x98\x81” … well, that’s one encoding of the UTF-8 encoding of the Unicode code point. > This is because setInterval(_=>{ },99) executes the function every 99ms This is categorically wrong. You can’t trust setInterval to heed your request precisely at all: it’s a request that browsers take as a minimum only. Most browsers will call your function after the number of mi…

Update: performance.now() will generally get you ~20µs precision now: https://blog.mozilla.org/security/2018/01/03/mitigations-lan...

Also I neglected to mention other frame rates; 60fps is the most common, but you do get some 144fps devices, where you’ll be looking at about 7ms delays rather than 16ms.

Post reply on HN