Dylan Schiemann

Last month, Microsoft created a document outlining each of the major browser’s deviations from the ECMAScript 3 standard. The blog entry links to the full 87 page summary which is pretty informative. For example, something as straightforward as parseInt(string, radix) has different behavior across browsers.

When radix is 0 or undefined and the string’s number begins with a 0 digit not followed by an x or X, then the implementation may, at its discretion, interpret the number either as being octal or as being decimal. Implementations are encouraged to interpret numbers in this case as being decimal.

alert(parseInt("08", undefined)); 
alert(parseInt("08", 0));
alert(parseInt("011", undefined)); 
alert(parseInt("011", 0)); 

Output:
IE: alerts 0, 0, 9, 9
FF: same as IE
Opera: alerts 8, 8, 11, 11
Safari: same as IE, FF

Dojo 1.0.1 has been released. Users of 1.0 are encouraged to update, and should have no issues with the migration. As mentioned previously, this release fixes 40+ bugs from 1.0, but there are no API changes.

Also, a quick reminder that SitePen will conduct a 2-day Dojo training course in Palo Alto in early December. Seats are still available. Please sign-up if you’re interested.

There’s been an increasing amount of talk recently about web 3.0, ranging from discussions of the semantic web, to discussions about significant improvements to user experience. The latter was an interesting article, because it describes how, in that authors mind, Dojo implements a lot of features he defines as web 3.0! Vector graphics and offline support have been important to me for quite some time, and we really are just starting to scratch the surface on the possibilities with these features.

Later today (Wednesday), Adam and/or Alex will push Dojo 1.0.1 live to the world. It’s been an odd year with holiday releases:

Easter Sunday: First 0.9 development milestone
US Independence Day: 0.9 beta
Halloween: 1.0 release candidate
Thanksgiving: 1.0.1
Christmas: 1.0.2 (planned)

There’s an updated Dojo 1.0.1 release candidate ready for download. This minor update does not change any APIs, but does resolve approximately 40 bugs in Dojo 1.0. Please give it a try and report any regressions. Assuming things go well, we’re releasing Dojo 1.0.1 on Wednesday in time for Thanksgiving.

I’ve been working with Karl on answering the question of “who uses Dojo”. We still have work to do to clean this up, but for now, check out the first few entries of the Dojo Spotlight.

Apple’s new Spaces feature in Leopard is great, but it lacks many of the customization options I like in the Tiger extension Virtue Desktops. Torrey recently discovered Proxi.app, which allows you to modify hot keys, and much much more.

JavaScript appeared in Thursday’s Dilbert… so bizarre.

I noticed the recent post on drupal.org that Scripteka, a predominantly prototype-focused site, is based on Drupal. It’s of course worth mentioning that the Dojo Toolkit uses Drupal for its web site as well, and later this year, the other Dojo Foundation project sites will likely start using Drupal as well. Not that Drupal is the easiest platform to work with, but it offers a lot of great community features making it as close to ideal as we could find for Dojo.

After years of loving Linkin Park’s music, in part because I love their sound, and in part because they had a good local following when I lived in Santa Monica, I’m saddened to learn that yes, all Linkin Park songs do sound the same. Yes Dylan, you do like listening to the same thing over and over again. As much as I enjoy Radiohead and the other 1000 interesting bands, I still listen to Linkin Park repeatedly. At least they don’t sound like Nickelback Levine, which I’ve been making fun of for quite some time.

And yet, I’ll still be listening to Linkin Park, because it has the sound that Dylan’s need (end Idiocracy reference).