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.

Sign up for GitHub

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

Jump to bottom

Is emem potentially useful or a waste of time? #2

Open
jstrimpel opened this issue May 8, 2012 · 1 comment
Open

Is emem potentially useful or a waste of time? #2

jstrimpel opened this issue May 8, 2012 · 1 comment

Comments

@jstrimpel
Copy link
Owner

No description provided.

@gihrig
Copy link

gihrig commented May 9, 2012

Interesting. I'm not deeply involved in JS development (more of a Java back-end-guy-looking-into-front-end), but...

  1. The value of Emem would seem to be dictated by the prevalence of JS memory leaks. Is this (now or in the near future) a significant problem? It seems to me that as JS plays an ever expanding role on mobile devices the answer might be YES!
  2. IMO, JS garbage collection should be done by the JS run-time (browser).
  3. An alternative use for Emem, could be the 'verbose' mode mentioned, as a debugging aide to locate event handlers set by multiple, unknown code fragments. That is, a map of all current event handlers, their source and status.

Hope that helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jstrimpel @gihrig