Infrequently Noted

Alex Russell on browsers, standards, and the process of progress.

new box

This blog has been moved to new hardware in a new NOC which should be significantly faster all around. If you experience any problems reaching this blog in the coming days, please send me mail.

speed

I love my Mac. I really can't imagine going back to windows or even Linux for my desktop at this point. But I've got a beef w/ the speed of this sleek little box that I spend the majority of my waking hours in front of. It's kind of a dog.

I recently put another gig of ram into it, which has kept it from the infernal swapping, but for straight-up development work, it's just not enough any more. I'd drop the cash on a new laptop today if Apple was selling something half-again as fast, but they aren't. The clock speed increases aren't fooling anyone. I need something that feels as fast as the thinkpads my friends are starting to tote around in lieu of their PowerBooks.

So c'mon Apple. Get it together so I can spend money with you again.

dojo, impending!

This week, Dojo will be releasing our first full public version, 0.1. It's not "fully baked" in a lot of ways, many things will change as we go into 0.2, and we already have a ton of things slated for past that, but 0.1 will be the best DHTML toolkit I've ever helped to build.

We've already started documenting some of the major parts of the system, and we'll continue that after 0.1 flys the coop. There's some really amazing stuff in there...can you say stable, lightweight, cross-platform WYSIWYG?

barcamp

I spent most of the day yesterday in Palo Alto at barcamp. The talks were great, the quality of people who have shown up is mind-blowing for a less than a week of organization. Big shout out to Chris for getting the whole thing put together.

Of note from yesterday were Ping's talk on anti-phishing techniques and the morning discussions about user-generated content; a discussion which turned to user-created content of almost every form.

I expect I'll be going back this afternoon to catch the tail end of things.

I feel truly lucky to live in a place where I can attend such things on a whim.

What's Missing in Deer Park

The Mozilla Foundatio...er...Corporation has released Alpha 2 of the next release of Firefox, and there's a lot of good stuff in it. On the whole, it feels faster, and tons of exciting stuff has already landed in this release.

Aside from E4X, it's hard to see how Deer Park is going to make my life much better as a DHTML developer, though. The story on rich-text editing is still grim. <canvas> is a disaster whose impact is only lessened by the inclusion of a minimal SVG subset. The platform is overall improving, but XUL apps still require enduring an RDF mind-fuck in order to get off the ground. Overall, you get the feeling that Deer Park is 2 steps sideways, one step forward.

But it wouldn't take much to change that from the perspective of the DHTML, nee, "Ajax" developer. Here are a couple of simple-ish things that would make our lives immeasurably better:

  1. Local string caching from script

    This is a strange name for a very very powerful capability: caching. Webdevs today need a coherent, simple, and workable local cache which can be accessed form script like any other object/hash and which stores only strings. Such a cache needs only a couple of properties to be wildly successful. Firstly, use the exact same-domain policy as cookies currently are subject to. Secondly, tell me (from script) how big the cache is and how much space is still free. Thirdly, let us specify expiry and flushing policies for it from script (not via HTTP headers). But please, whatever you do, do NOT over-think this problem.
  2. Event-transparency in the z-order and positioned event generation

    Allow developers to specify that a particular DOM node is "transparent" to DOM events. Which is to say, it passes them "down" the z-index stack without triggering a dispatch or bubble sequence in any way. This should probably be handled by a "-moz-" prefixed CSS attribute. Related to this, let us generate DOM events at a set of coordinates without knowing ahead of time what the node we want to route the event to happens to be. Both of these capabilities are amazingly important for a whole set of graphical apps that Deer Park is about to make available.
  3. Improve Venkman's profiling output

    Venkman is the most powerful tool in the professional DHTML developer's toolkit today, but it's crippled when it comes to outputting useful data from it's profiling tool. Either try harder to assign names to anonymous functions or at least make the output something that can be loaded by gprof. The current situation is amazingly painful, but since it's the only game in town, we live with it.
I know they don't sound like big features, but they're tremendously important to the kinds of rich applications that Deer Park is supposed to be enabling. The big push now is to keep Microsoft from breaking the web with XAML, and I think we all know it. Small, obviously beneficial changes like these go a long way toward maintaining and improving the viability of the open web as a platform.

Older Posts

Newer Posts