4 ms·
Was OP referring to the fact that V8 namespace is available inside JSFiddle? Because I was a bit surprised about that and made me wonder if opening this JSFidd
by whoisjuan 6y ago
Was OP referring to the fact that V8 namespace is available inside JSFiddle?
Because I was a bit surprised about that and made me wonder if opening this JSFiddle on Safari would work at all (I’m on a phone so I can’t test).
- darkerside 6y agoThat's funny. Not at all the way I read it, but it could totally be read that way. Made me do a double take. Still, I think my original reading is correct, because I don't think there is any issue with the "quality" of v8 inside of jsfiddle. While imagining Chrome doing its best to identify real words in long strings of Japanese text and failing spectacularly just made me laugh again.
- yftsui 6y agoThe fiddle doesn't work on Safari. TypeError: Intl.v8BreakIterator is not a function. (In 'Intl.v8BreakIterator(['ja-JP'], {type:'word'})', 'Intl.v8BreakIterator' is undefined)
- polm23 6y agoOP here, I was not referring to it working JSFiddle, just the idea of Chrome shipping with a Japanese tokenizer. I've known people to do stuff like compile MeCab with emscripten to get Japanese tokenization in Electron, so the fact that the functionality was there already (even with lower quality) was surprising.