Rarely do I ever command you to do something but I've watched this video three times now and I'm completely mesmerized by Douglas Crockford's tech talk, JavaScript: The Good Parts. During this hour long talk, Douglas Crockford shares his insight about both the good and bad parts of the JavaScript language. He covers the language's embarrassing misteps, its valuable hacks, and its powerful features.
I can't recommend this video enough. It's funny, educational, and enlightening. Even if you can only leave the audio on in the background, you must give this video a listen. Crockford wrote a JavaScript book with the same title which I cannot speak for.
Once you've had a chance to listen, share your thoughts -- what are you favorite "good parts" of JavaScript? What really burns you about the language?
One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?
Feature detection via JavaScript is a client side best practice and for all the right reasons, but unfortunately that same functionality hasn't been available within CSS. What we end up doing is repeating the same properties multiple times with each browser prefix. Yuck. Another thing we...
As more devices emerge and differences in device interaction are implemented, the more important good CSS code will become. In order to write good CSS, we need some indicator about device capabilities. We've used CSS media queries thus far, with checks for max-width and pixel ratios.
The HTML5 revolution has provided us some awesome JavaScript and HTML APIs. Some are APIs we knew we've needed for years, others are cutting edge mobile and desktop helpers. Regardless of API strength or purpose, anything to help us better do our job is a...
Absolutely second this post – awesome tips and principles for balancing idealism and pragmatism in a language where both can leave you high and dry, scratching your head wondering what went wrong…
You can’t possibly listen to Crockford and not learn something new. Don’t even try.
Wow. I figured he would be telling me stuff that I already knew, but he keeps on revealing amazing amounts of information that will improve my code significantly.
Absolutely second this post – awesome tips and principles for balancing idealism and pragmatism in a language where both can leave you high and dry, scratching your head wondering what went wrong…
You can’t possibly listen to Crockford and not learn something new. Don’t even try.
Wow. I figured he would be telling me stuff that I already knew, but he keeps on revealing amazing amounts of information that will improve my code significantly.
Just blew me away.
errr…. I don’t see any link to the video, am I missing something?
my bad, video did not show up the first time
Really nice… I learn a lot of things… mostly in the Object part, I was missing over there… Thanks for post it!
Cheers.
No one laughs at Steve, and everyone chuckles with Doug. (No real value, I know, but JavaScript developers should watch this).