I am cranking through some code examples and plenty of research for this thing. It should kick incredible amounts of JavaScript ass. Come to think of it, it's a ninety minute presentation, so it better kick ass I'm going to look at load times, execution times, ySlow scores, codebase and add pure editorial commentary for several popular libraries (at minimum, jQuery, YUI, Prototype, and Dojo), as well as pure JavaScript and my own bare-bones library.

If you're a Boston JavaScript nerd, I hope to see you there.

Here's the description:

Our next JavaScript Meetup will be held on Thursday, April 30th at Microsoft Research Center located at One Memorial Drive in Cambridge. You should come to the 11th floor to be let in. There is also parking available at a cheap evening rate in the building.

Rob Larsen , Principal Presentation Engineer at Cramer, will demonstrate comparisons between raw JavaScript and utilizing the more popular JavaScript libraries currently available.

After the presentation | demonstration, we will go around the room introducing ourselves and asking the group for advice | opinions on any JavaScript-related issues members are facing.

Microsoft will provide pizza again. What a nice company!

Please RSVP and bring guests. We always have lots of pizza left over.

And the meetup.com link:

April Boston JavaScript Meetup Meeting – JavaScript Library Comparisons – The Boston JavaScript Meetup Group Cambridge, MA – Meetup.com

I've run into an issue of nomenclature over the past couple of years and it's finally turned into a "thing."

What does one do with "things?"

If you answered, "write about them," you got it in one.
(more…)

Got firebug? Load this test page: Simple Style Graffiti Canvas and watch as I load the "previous" and "next" pages with XHR, parse out the image tags in each, adding them to the users cache.

Is there any reason I wouldn't want to do that?

The performance benefit in the browser is a huge reason TO do it.

But what about the flip side?

I'm already thinking about the extra requests that might not be actually used by visitors who don't follow the back and next path? Those could add up maybe. If I implemented this my site would handle an extra 3 php requests per initial page load and then two cached requests and one new request each additional page. But, that doesn't seem like a big deal to me.

Again, am I missing something?

Anything else?

If you are, I just stumbled across this:

AutoSuggest: An AJAX auto-complete text field : CSS . XHTML . Javascript . DOM, Development : Brand Spanking New

I think it looks pretty slick.

I think I'll be running through this after lunch, myself.

ScribeMedia » Firefox 2 and Javascript with Brendan Eich