An overview on how jQuery code is organized, what parts are good and bad, and insights on the plugin system and one of the most complex parts of it: the internal event handling.
◦ Some μ-optimizations built-in (e.g.: #id). • Failure on it triggers full Sizzle engine ◦ :first-child on IE7 ◦ :visible on any browser • Some valid selectors are also ran by Sizzle!
way shorter than jQuery.prototype • Instances are created regardless of the “new” keyword • “init” prototype is the same as “$” prototype, so the inner trick looks transparent
all events at once! ◦ List events attached! • Standardizes interface for attaching and triggering native & non-native methods • Solves quirks on the “event” object