#Ideas

November 7, 2006. Adobe gifts 135,000 lines of code to Mozilla in the form of Project Tamarin, a Javascript Virtual Machine compliant with the still-not-fully-implemented ECMAScript 4. Mozilla would try a few times to incorporate Tamarin into Firefox, but would eventually abandon that idea for performance reasons.

Still, it injected some enthusiasm into adopting more modern Javascript standards, pushing the web forward at a time when it really needed that.

#Bookmarks

I quoted from Interface Culture by Steven Johnson recently.

He also once said this in an interview (emphasis mine)

I suspect, I’ve been incredibly energized by all the grassroots Web 2.0 applications that have exploded over the past few years, most of them descendants of Firefly in one way or another. (Someone — and come to think of it, it’s probably me — should go back and track all the core ingredients of today’s Web that were visible at Firefly circa 1996.) 

That parenthetical is my current project. It’s taking me in all sorts of directions.

In Zen and the Art of Motorcyle Maintenance, Robert Pirsig muses—among other things—about the intersection of art and technology, and what is lost when the two diverge and we seek out only the cold refuge of science.

We have artists with no scientific knowledge and scientists with no artistic knowledge and both with no spiritual sense of gravity at all, and the result is not just bad, it is ghastly” (Time for real reunification of art and technology is really long overdue)

I think in our modern web, the small, personal web is where I see art and technology merge again. There is a lot of possibility in that.

#Bookmarks

Jamie Zawinski makes the case that enabling DRM in the browser was the open web’s original sin. When the W3c, and subsequently Mozilla, caved to pressure from commercial interests, it opened a crack in the founding ideology and spirit of the web and allowed a near endless commercial erosion of the open web.

Fortunately, Zawinski has a solution.

In my humble but correct opinion, Mozilla should be doing two things and two things only:

  1. Building THE reference implementation web browser, and
  2. Being a jugular-snapping attack dog on standards committees.
  3. There is no 3.