aspose file tools*
The moose likes HTML, CSS and JavaScript and the fly likes Memory leaks with script.aculo.us? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » HTML, CSS and JavaScript
Bookmark "Memory leaks with script.aculo.us?" Watch "Memory leaks with script.aculo.us?" New topic
Author

Memory leaks with script.aculo.us?

Charles McGuire
Ranch Hand

Joined: Jan 18, 2005
Posts: 99
Hi Christophe

Recently I was at the GWT conference in SF, when a question came up about using JS libraries. The folks at Google do a pretty darn good QA job on GWT and provided lots of charts on different behaviors in different browsers of different versions.

In the session, it was hinted that script.aculo.us had a problem with memory leaks. I can't remember if it was script.aculo.us by itself or just with another browser, (IE 6.0 is a steaming pile of memory leaks by itself, but I digress) but I was curious as to your about the stability of that particular library.

Second question: I wish I could thumb through your book. I was on Amazon reading the reviews to get a feel for the book. Will it be available through bookstore channels (Borders, B&N, etc.), do you know?
[ February 14, 2008: Message edited by: Charles McGuire ]

There's no place like 127.0.0.1
Christophe Porteneuve
Author
Ranch Hand

Joined: Jan 28, 2008
Posts: 43
Hey Charles,

About stability and memleaks: aside from the numerous leaks one can easily get from IE, I do not believe Scripty suffers from memory leak issues (or if it does, they're too tiny for me to experience in Scripty-intensive apps I keep open for weeks on end and use every other minute).

Thomas and I would sure be interested in getting details and reproduceable use cases, especially if they come with unit-tested patches :-)

It would also be interesting to know which version of Scripty the GWT team was alluding to. Plus, Scripty 2.0's effects engine was rewritten from the ground up and is way different internally than its 1.8 counterpart, so if an issue existed, it may well be gone in the next release.

Regarding the book: AFAIK, it's available wherever books are sold. I know Barnes & Nobles has it (and is often sold out on it, too, even the huge NYC one!), and the book certainly sells through regular retail channels.

I wish Amazon would publish reviews in a timely fashion. I've been getting reports of a dozen reviewers who can't understand why their (glowing) reviews don't show up on the book's page� If you want to peruse, you can always look at the couple excerpts on the book's page at Prag Prog.

Cheers,


Christophe Porteneuve aka TDD
"They did not know it was impossible, so they did it." --Mark Twain
Pragmatic Guide to JavaScript: http://books.pragprog.com/titles/pg_js/
Prototype and script.aculo.us: http://books.pragprog.com/titles/cppsu/
Charles McGuire
Ranch Hand

Joined: Jan 18, 2005
Posts: 99
Sorry Christophe. I don't have the specifics for which you are asking. All the sessions from the conference are on YouTube, but even if we find the specific reference you won't get the detail you're seeking.

One of the appealing things about GWT is that it insulates the developer from knowing a lot of JavaScript. For example, I work in a small development department and we have to be careful about spreading ourselves too thin over too many technologies. Unfortunately, management makes us support what we create and put into production (the gall of them!)

Am I correct to infer from answers you've given elsewhere in this forum this week that your techniques (and JS libraries you use) have sort of the same goal, that is, leverage library code and don't become JS Ninjas? Or do you advocate the path to total master of JS to become one with the language?
Christophe Porteneuve
Author
Ranch Hand

Joined: Jan 28, 2008
Posts: 43
Hey,

Am I correct to infer from answers you've given elsewhere in this forum this week that your techniques (and JS libraries you use) have sort of the same goal, that is, leverage library code and don't become JS Ninjas? Or do you advocate the path to total master of JS to become one with the language?


Prototype/Scripty certainly endeavor to spare developers this mastery requirement by making scripting as simple, concise and elegant as possible.

However, I do believe that JS is the Next Big Language, as Steve put it. But that doesn't mean everyone should have to become a master; to each their needs�
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Memory leaks with script.aculo.us?