Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wasm could be smarter about spans #700

Open
gdamore opened this issue Mar 4, 2024 · 1 comment
Open

wasm could be smarter about spans #700

gdamore opened this issue Mar 4, 2024 · 1 comment
Labels

Comments

@gdamore
Copy link
Owner

gdamore commented Mar 4, 2024

Right now the WASM tcell.js is completely ignorant and treats every cell as it's own thing, with no knowledge of what is in the next cell over.

For the terminal based implementations we are very careful to avoid doing this, because it takes a long time to send that data. That can be the case for the web based situation as well. But all these spans also probably put a lot of extra work on the client to render this. There have been complaints about the web assembly being slow, and this is likely one significant contributor.

@gdamore gdamore added the wasm label Mar 4, 2024
@gdamore
Copy link
Owner Author

gdamore commented Mar 5, 2024

I've become convinced that we should just convert to using xterm.js.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant