I was supposed to give a talk in Amsterdam yesterday, but as the airlines would have it, there was no such luck.
I got as far as Houston in my trans-continental journey before being stymied by aggregated air travel stupidity. Luckily, Andy Smith of Flock fame stepped into the breech and gave the talk in my place.
The talk was written out ahead of time and Andy can read better than I ever could, so I assume it went as well as possible. At least he didn't report any sharp objects being thrown at him afterward.
The text of the talk is here.
Tomorrow is my last day at JotSpot.
For some months it has been clear that the Dojo is now on a path that requires more hands-on management, and either I can choose to double-down or get out of the way. People use the word "vibrant" to describe the Dojo community, but I think that hardly begins to cover it. The amount of traffic on the Dojo lists is stupendous. Contributions and committers are coming out of the woodwork, companies are looking to Dojo for a solid platform to build on, and our next release has been languishing. Clearly something has to change.
At the same time, I care deeply about Jot. Yeah, I know, companies can't love you back, but Jot is an amazing place, has a truly unique product, and is chock full of people I'd love to keep working with.
My friends have had to put up with this kind of agonizing for months now.
I don't talk much about Jot here, and I think it's probably because of the classic engineering apathy towards marketing. All I see is my bug list, not the cool stuff we just built. But now I've got a little time to reflect.
Jot isn't a Wiki. Not really. It may also be the most kickass wiki the world has ever seen, but in many ways that's incidental to the overlap with the core system capabilities. I often say that "it's an application platform cleverly disgusied as a Wiki", but that doesn't really capture it. When people think "application platform", they see something that requires them to set up a database, install some gunk, get Apache correctly configured, get the rest of the environment bootstrapped, and then voila! Programming nirvana. A lot of these supposedly "elegant" platforms require that you cough up this giant configuration hairball before you can even start. The justifcation for
this seems to usually fall into either the "but we're using a pretty language!"
or the "we're using the standard business language!" buckets.
Now, of course, I too used to accept the apache-database-blah-blah-blah dance
as a cost of doing business. But as with most things where there is an entire
business devoted to making something just appear to happen magically (web
hosting), these businesses are just filling in the gaps until the root
inefficency can be elided entirely.
Jot represents the first system that I've ever seen that gets this right.
Instead of forcing you to think about some kind of MVC fuss-and-bother, you
build what you were after in the first place, usually a form, and then start
iterating on the implied structure of that data.
You don't change a model and upgrade a schema, you just add the property you
wanted to add. This has been the secret to building applications like Tracker. We don't worry about a data model
when building apps like this. The data evolves as our understanding of how
people will use the UI evolves, and because it's all versioned, experimentation
In the same way that test-driven coding allows you to make changes with
confidence, the deployment environment playing "version nanny" is a great
liberator in development freedom and process. Loading anything, data or
program, into the system has the effect of strapping the suspenders on, and
isn't that when you really need them? Not when it occurs to you that you might
be doing something destructive, but at the point where you might otherwise
be doing something destructive.
Add to that some awesome Dojo integration with Jot (which I'll talk more about when the new version hits the servers), and Jot really is the first of the next generation of application platforms. Web services make the configuration dance transparent on the macro scale, and Jot can do the same thing for apps on the local scale. It's a level of power that I've never encountered before, and don't expect that I will again anytime soon.
Wednesday is my first day at SitePen.
Dylan has quietly been "getting the band back together" under the umbrella of a small consulting firm that he helped to found back in The Day (TM). SitePen is nothing short of the A-Team of Dojo-based application development. In addition to employing two of the project's co-founders, a large number of
core Dojo committers are working on projects large and small for a diverse set
of clients who value great UI married to top-notch engineering. Along with the
great guys at TurboAjax, SitePen helps to
fill in the gaps that the Open Source nature of Dojo leaves unfilled.
But what about that whole "need to spend more time on Dojo" bit? Well, SitePen
is hiring me to work on Dojo full time. Sure I'll be fixing
high-priority bugs for SitePen customers, but all of my work will be rolled
into the Open Source project. Most of the time though, I'll be focusing on what the community needs and how we can best make the project's goals of universal adoption a reality.
My new job will be to push Dojo forward as fast as we can possibly make it go.
There's a long list of improvements for Dojo that I've been putting to the side
for when I stumble onto a large pile of "free time". SitePen is going to allow
us to make those things a reality.
Time to see how high this "Dojo" thing can really fly.