3 ms·

See the comparison: https://github.com/coder/ghostty-web?tab=readme-ov-file#comparison-with-xtermjs https://github.com/coder/ghostty-web?tab=readme-ov-file#comp

• ghthor 10mo ago
  Any chance that it can take advantage of webgpu, or is it already doing that from this wasm build?
• svat 10mo ago
  The comparison has two points one of which says that for "Complex scripts (Devanagari, Arabic)", ghostty-web has " Proper grapheme handling". But when I tried something extremely simple at the https://ghostty-web.wasmer.app/ https://ghostty-web.wasmer.app/ or https://ghostty.ondis.co/ https://ghostty.ondis.co/ demos (just `echo "कवि"`), it failed pretty miserably (and in different ways in the two demos). So I'm not sure what to make of it. (Seems slightly better in the actual Ghostty app, but not in any usable way: here was my comparison last year https://shreevatsa.net/post/terminal-indic/ https://shreevatsa.net/post/terminal-indic/ and Ghostty is comparable to the other terminal apps, better than some, worse than some. Anyway the fact that it works in Ghostty but not in ghostty-web casts doubt on “Ghostty's emulator is the same battle-tested code that runs the native Ghostty app”. Do you understand what is going on?)
  • kylecarbs 10mo ago
    I'll take a look - not sure what's going on. I'll remove it from the README for now since it's not working in the demos. Thank you for letting me know!
  • sreya 10mo ago
    It's very much the same emulator but we're exposing a subset of functionality via WASM, in this case it wasn't handling grapheme codepoints correctly. It should be fixed on main (or @next).