+1

This thread on Lambda the Ultimate talks about multiple implementations of JavaScript with some combination of (serializable) continuations, tail call elimination, and serializable threads. The referenced Kelsey work is on Kali Scheme, a distributed Scheme that allows you to send closures (objects) and continuations in messages.

Bill de Hora describes how to do faceted classification with a Wiki.

Nick Lothian invents the Fiki: a Wiki that automatically figures out where links should be created

Sam picked up on Elizabeth Lane Lawley's post on Wiki backlash, and a flow of comments ensued. The major issue that's come out of this for me is the ahistoricism of Wikis, or put another way, the non-traceability of a Wiki. If people are working intensely with each other, then a Wiki is fine, but as the process runs out over time, and more people join the conversation, it's nice to have a way to trace how you got there. Some Wikis let you see all the changes, but its kind of like reading CVS diffs. You can do it, but it's not always the best way to trace the flow of discussion and decision. We've been using a Wiki at the ASF, which is my first real use of one, and it's been successfull for small documents that don't link to each other that much. But for big documents or multi-multi page layouts like the pie/atom/necho wiki, it's tough unless you can devote attention to watching the changes every day. I've found the same difficulty with the OSAF Wiki. The OSAF Wiki is easier, because there are far fewer small edits. It tends to be (relatively) infrequent big updates of large sections. It's like you need an out of band channel to hold the rationale and traceability of what's happening on the wiki. What that out of band channel is, I'm not sure. But then you need a way to link them to achieve traceability.

Ben Goodger posted on the movable type forum, to let them know what was in store.

Asa Dotler reveals more cool stuff that you can do with web panels: grabbing any page into a web panel. This sort of sound like a Haystack UI continuation, but that's not exactly right. But the idea is there. You bring up some UI interaction (browser based), you need to stop in the middle to find info for it (like a link to insert), so you can freeze the interaction into the web panel.

Phil Rignalda calls web panels Firebird's next killer feature. This would be after tabbed browsing and popup blocking (both of which debuted in Mozilla).

Ben Goodger has made it possible to selectively disable plugins in Firebird, so that instead of viewing Quicktime, Acrobat, and other files inline, you can download them instead. It'd be even nicer to be given the choice.

There are a lot of nice feature in Firebird and going into Firebird -- I'm almost ready to stop using Mozilla and switch over to Firebird (I've already moved onto Thunderbird). Both Firebird and Thunderbird have the buzz around them. There's energy, and activity. The cool stuff is rolling in quickly. It seems like all of a sudden the guys have hit their stride. Not like they weren't working hard before. Maybe its the Mozilla Foundation, maybe its the ability to drop all the cruft, who knows. But these folks are picking up velocity and thats good for them, and for us.