Last week we released Dojo 0.9, and while we're excited at how well it performs, how easy it is to use, etc. but the proof is in the apps. In particular, Plaxo Pulse, AOL's TinyBuddy (app here) and the new Bloglines beta are all 0.9 based and the experience really shows it. They're all "data stream" apps, things you fire up and then leave open or spend lots of time in, and they're amazingly useable, responsive, and useful. If you haven't tried them out, now's the time to give them a whirl and get a feel for how 0.9 is helping real apps rock.
SitePen is hiring.
To be honest, SitePen is usually hiring, so why the blog post? Because I'm hiring for a SitePen R&D Associate. This isn't your average programming job. Not only will all the work from this new position be released as Open Source software,it's a self-directed research job. Combined with SitePen's completely-virtual structure, you can work on what you feel is important and live wherever you want.
Read on for the full description:
R&D Associate (title negotiable)
<p> SitePen is a fast-growing services company with deep roots in Open Source web software and an ongoing commitment to give back to the Open Web. The problems we solve for clients sit at the intersection of Computer Science and Interaction Design while cutting across a wide variety of problem domains. As an R&amp;D Associate at SitePen you'll be responsible for investigating and developing solutions to the thorniest problems in real-world web application development and since everything you do will be Open Source, your impact will be both meaningful and lasting. </p> <p> Some topics currently of interest to SitePen include: </p> <ul> <li>web framework scalability</li> <li>parametric CSS</li> <li>ES3/ES4 implementations across VMs</li> <li>publish/subscribe messaging and scalability</li> <li>web-based interaction design/analysis tools</li> <li>Open Data portability and metadata normalization</li> <li>browser-based data visualization</li> </ul> <p> But those are just the problems that keep us awake at night. What we're <em>really</em> interested in is hearing about how you'd like to make a difference in the evolution of the web. At SitePen, you'll have the freedom to pursue your interests and a mandate to work with broader communities to make your ideas reality. </p> <h3>Required Qualifications</h3> <ul> <li>contributor to at least one Open Source project (active committers preferred)</li> <li>fluent in one functional or scripting language (C experience a plus)</li> <li>must be able to author technical papers</li> <li>must be comfortable presenting and defending work to groups of various sizes</li> <li>permanant legal right to work in the United States</li> </ul> <h3>How To Apply</h3> <p> Send a plain-text email to "firstname.lastname@example.org" with the subject line "R&amp;D Associate Application". In the body of the email, please explain why you think you'd be good for the job, what research interests you would like to pursue, and if you have one, a link to your website/blog. Please include links to your Open Source involvement and note major contributions (planning, design, features implemented, research contributed, UI/UX/IxD, etc.). Also, either include a link to an online resume or attach one in plain-text or PDF format. </p> <p> There is no deadline for application, but the earlier you apply the better your odds. </p> <h3>Benefits</h3> <ul> <li>Senior Engineer grade pay</li> <li>Comprehensive health insurance</li> <li>All work product Open Source</li> </ul> <h3>Additional Information</h3> <ul> <li> <b>Location:</b> anywhere you damn well please. SitePen is an entirely virtual organization. </li> <li> <b>Travel:</b>10-25% travel, depending on personal choices regarding conferences and symposiums. Presenting papers and speaking on your work is encouraged. </li> <li> <b>Job Type:</b> Full Time </li> <li> <b>Reports To:</b> Director of R&amp;D (Alex Russell) </li> </ul>
Uniquely for an R&D job, there are no minimum education requirements. We only care how effectively you can advance the state of the art on the Open Web. If that sounds like a calling you can get behind, I'd love to hear from you.
Scott Beale's Paradise Lost party was outstanding. Jennifer and I have kind of "dropped out" of the Web2.0 scene for lots of very obvious reasons, but every now and again it's wonderful to see everyone. Folks were bummed about the lack of the planned fire displays (darned city permitting!), but the Photo Boof was awesome.
I'm back from OSCON, and while I spent more time holed up in my hotel room working on slides than I would have liked, it was a thought-provoking trip. OSCON, unlike a lot of conferences, does a great job of getting "the right people on the bus" by not tying itself to a particular technology. Full disclaimer: I was ostensibly on the OSCON program committee this year, although I was mostly a slacker about it. The hallway track this year was particularly strong. The evolved term for what OSS enables seems to be "participation", and OSCON really keeps getting to the heart of that.
Just before the official OSCON start this year was "Ubuntu Live". I didn't have an opportunity to go, but its very existence says something important about a transition that seems to be happening in the OSS world. Yes, ORA is also transforming into a conferences company with an incidental publishing arm, but I don't think that explains all of it. There are still religious partisans at gatherings like OSCON but more and more of the folks I talk to (self selection?) are "socially Open Source" people, and that's leading (I hope) to a re-balancing of priorities inside the projects they are involved with. Instead of just focusing on how free something is (in whatever sense you prefer), there's a sea change which focuses also on the end user experience. This seems long overdue and a good sign. Focusing exclusively on the user experience without any attention to negative externalities leads to a world which I wouldn't want to live in, but when there is tension between them there is hope for progress. It's market competition, but not in the sense of products jockeying for dominance (although that's one of the ways it is expressed). It's competition in the marketplace of ideas. It prompts important questions like:
- What does the web (and sites like Facebook in particular) imply for the state of competition in services?
- Is Open Data sufficient to ensure user freedoms and a functioning marketplace?
- What does it mean to be transparent and encourage participation?
- Who owns it? What rights do (and should) others have in a world where a third party always mediates everything?
- When a company "gets involved in Open Source", what should users expect other than lower prices? Should there be a code of conduct for OSS-involved firms? What are the communities responsibilities to those firms?
In fact, I suspect that the web is playing an under-valued role in this transition. Since the web is partially open by default, it closes many of the solved questions for practical intents and brings the questions of data and community and design/experience into sharp focus. How will OSS projects handle them? Can existing project structures even being to address them? We're struggling with the last one daily in Dojo.
The assumptions of OSS have always been that there's some relatively open commodity platform which is mostly knowable, but what happens when you depend on web services or plugins which behave like hardware; sans ownership? What's the imperative for the OSS community to build full web applications and services now that the desktop application is clearly on the wane? How will we address the fundamental, centralizing architecture of the web without resorting to religious discussions? What is the implication of not having an open, ubiquitous platform for user experience design and analysis?
I think these are questions that the Dojo Foundation should start to wrestle with. The answers to them may not come from us (although "us" is anyone who wants to get involved), but I'm strongly in favor of the Foundation trying to find ways to think about and address them.
A last-minute schedule change got me home to catch the last day of TAE. Having given 2 talks earlier in the week, it was great to catch sessions without stress. Like OSCON, the vibe at the last day of TAE was very low-key and hype-free. Seems the breathless nature of "AJAXWorld" may have finally blown the chaff away, leaving TAE and other smaller conferences to provide the beer-and-ideas atmosphere that is so desperately needed to keep things moving forward.
First, I'm gonna be at OSCON the same week that TAE is going down. If you were counting on me buying you beer while in SF, you'll have to collect from Dylan (he's good for it) or one of the other Dojo's.
Next, can y'all please stop conflating Comet with a particular HTTP-level mechanism for achieving the stated user interaction goal? It's getting quite tiresome to hear folks say things like "long polling or Comet" as though they're different. The XMPP HTTP binding guys even go to great lengths to explain how their Comet technique (BOSH, aka: "long-polling") isn't Comet. Almost as entertaining as it is wrong. Long polling along with other techniques are ways of implementing the basic Comet pattern. The general description of the pattern contains no preference for one or the other. It only requires that you not naively poll N seconds.
Lastly, I'd like to express my disappointment that Jack didn't include Dean's excellent Base2 in his latest round of benchmarks. It's doing us all a disservice that he's not including the fastest engine around in his benchmarks.