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

Improve spell editor performance #17

Closed
nwinter opened this issue Jan 1, 2014 · 2 comments
Closed

Improve spell editor performance #17

nwinter opened this issue Jan 1, 2014 · 2 comments
Assignees

Comments

@nwinter
Copy link
Contributor

@nwinter nwinter commented Jan 1, 2014

I keep getting bug reports like this: "During casting, sometimes everything got extremely slow and it became almost impossible to type. It made me worry I was going to lose my work, since it's hard to even select the code when it's stuck like this."

I never see it, but maybe my computer is too fast? I don't know. I can probably fix it anyway, although if anyone who does see these kinds of problems wanted to dig into it with the Chrome profiler or something, that'd be awesome.

One thought: move Aether's linting and parsing and such into a web worker? We're going to all this trouble to avoid blocking the main thread by linting and parsing and transpiling too often, but we could do it more often and not have performance problems if we did it in the background instead.

@ghost ghost assigned nwinter Jan 1, 2014
@schmatz schmatz assigned schmatz and unassigned nwinter Apr 17, 2014
@schmatz
Copy link
Contributor

@schmatz schmatz commented Apr 17, 2014

I'm now starting work on this issue.

@schmatz
Copy link
Contributor

@schmatz schmatz commented Apr 18, 2014

I've got background linting done now, currently moving hasChangedSignificantly onto a worker to not have it block the UI. Should take a bit of time to implement, but improve editor performance for large programs quite a bit.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.