I generally try to listen to JavaScript/development podcasts and videos when I'm working. It's a great way to continue to learn and get ideas while doing the ho hum programming busywork that's unavoidable. Here's a great Google Talks presentation that was given last summer about JavaScript and speed.
After you watch some of it, let me know what you think. Oh, and trust me, I've seen your JS -- you need this.
Regardless of your stance on pornography, it would be impossible to deny the massive impact the adult website industry has had on pushing the web forward. From pushing the browser's video limits to pushing ads through WebSocket so ad blockers don't detect them, you have...
I work with an awesome cast of developers at Mozilla, and one of them in Daniel Buchner. Daniel's shared with me an awesome strategy for detecting when nodes have been injected into a parent node without using the deprecated DOM Events API.
Honesty hour confession: file uploading within the web browser sucks. It just does. Like the ugly SELECT element, the file input is almost unstylable and looks different on different platforms. Add to those criticism the fact that we're all used to drag and drop operations...
I get quite a few support requests for my previous MooTools SmoothScroll article and the issue usually boils down to the fact that SmoothScroll has become Fx.SmoothScroll. Here's a simple usage of Fx.SmoothScroll. The HTML The only HTML requirement for Fx.SmoothScroll is that all named...
Wow… is my scripting really that bad?
It’s refactoring time :D
Thank you for sharing, huge help and now i’ve got gobs and gobs of javascript to go refactor. :)
Thanks for sharing.
I will also have to re-write some of my code.
I’m wandering if Mootools should remove .each(); to encourage good performance practice? Or at least put a note in the documentation warning that it will slow down the code…
Also, is DocumentFragment use in Mootools to speed accessing the DOM?
Well, removing the each() function is not the solution I think… How would you make a sortable list or something like that dynamically? I don’t know another solution for that, you’ll have to select EACH element so you use an each function I gues…. Maybe David does?
How do I track the execution time of my script in several browsers? I’d like to see what kind of improvement I’ll make when I’m adjusting my scripts and classes.
Awesome video, currently in the process of writing it up into a full blog post and I came across something pertaining to MooTools
Does the method “setStyles” cause multiple reflows?
[code]
element.setStyles({
height: “100px”,
display: “block”,
fontsize: “130%”
})
[/code]
will that cause 1 or 3 reflows?
Thank you for a good link and Mootools, David!
I’m just the user of Moo, I like it. Only one thing that makes me unhappy with moo – is to much time, required for library initialization.
I’m constantly optimizing my servers and sites to give users faster and earler page view as much as I can and the last bottleneck is JS library initialization time.
When I’m looking at Firebug in FF I see mootools is blocking all images , asking browser to wait for it’s initialization. It takes about 0.5-0.8 seconds for browser to figure out that it can continue load multimedia objects on page after mootools load.
0.5-0.8 seconds is significant for me, becose some of my users have too much hops (asia) to my servers and usually pages is loading in 1.5 seconds. 0.8 – is the half (!), not filled with any useful actions page load time, too big comparing with total page load time.
Yes, mootools is loading from page header.
According to YSlow or Page Speed recommendations I could move mootools to the end of the page, but I’m worry about document.write calls, that could not modify page objects in some initialization functions that you’re using and I donw’t deeply know…
So my questions is:
1) Can I do “late” or “parallel with loading static multimedia objects” initialization of mootools library somehow?
2) can I safety move whole mootools (or some parts of the library) to the page bottom to prevent browser blocking on objects loading?
3) what methods you’ll advise to speedup parallel page loading with whole (core and nc) mootools?