(this is page 77 of 121)





Latest

Mind bending Javascript

For anyone who works on the web and grew up in the 80s playing the original Nintendo Super Mario Bros. who wants to have their mind bent (in a good way), go and check out an implementation of the game in pure Javascript, downloadable as one 14kb file!

It is a true sign on how many processor cycles we've gained in the past 25 years that this can be done in a high-level language meant to execute simple web scripts.

Whenever I see folks on the bleeding edge of web development pushing the envelope like this, I think of that old Apple commercial that celebrated the crazy ones who just "think different" and show the rest of us how much is starting to fall under the realm of the possible.

Update: John Resig has done a great dissection of how the data is packed in one file.
Comments Permalink

I'm gonna be writing about Google's AppEngine for a while as it strikes me as one of the most interesting moves in the evolution of the web-as-platform that we've seen in quite a while. So let me get the boring stuff out of the way first...

A couple of years ago when Tabblo was a struggling startup in need of any and all distribution, I visited a senior executive at Yahoo who supposedly had a nose for new and interesting personal publishing applications. Our hour together quickly devolved into him trying to convince me that we should abandon our own user authentication system for Yahoo's recently announced browser based authentication. As he pitched and I listened all I could think was: yeah right, and what happens when one of your competitors is interested in doing a deal with us?

These things shouldn't matter when considering platform-level services— after all, very little of Tabblo's special sauce came from the way we authenticated users (except for maybe some of those "special" security holes). The reality though is that when what you're building is intertwined with a emergent business model, these platform decisions are just as much politically driven as they are technically motivated.

And as Google joins Amazon in racing to provide web developers with critical bits of cloud infrastructure, we're about to see politics come to the fore again. Fifteen years ago, the question was: are you writing for Mac or PC? Today it is: are you writing in Rails, PHP, or Django? 5 years from now it will be: are you on Amazon's cloud or Google's?

Dave Winer was the first to point out that Google's move to open its platform to developers was a smart tactic to grease the skids for acquired startups— after all, if you are already running on the Google cloud, assimilation post acquisition is an easy task. And trust me, on a week when we're struggling to move just the hardware from Boston to Austin to get more compliant with HP's IT infrastructure, I can really appreciate this point.

But ultimately I think it's wrong if only because it seems to me that Google's acquisitive binge may be coming to a hiatus of indeterminate length due to maturity of its own business and greater macroeconomic forces. When looked at it from this perspective, AppEngine makes even more sense: why buy the pageviews outright when you can just toll them? All of those great arguments about long-tail application notwithstanding, letting others take the product risk while they ride on the back of your platform seems to be a much better bet to make.

And by the way, as far as platforms go, this one feels like a winner to me, even after only 30 minutes of perusing the SDK and docs. Unless Amazon moves quickly to integrate its own stack, S3/EC2/SimpleDB is going to feel like DOS in Google's Windows world. The latter's integration of the stateless webapp model, its own super scalable persistence layer, and a number of great open source pieces of infrastructure (way to use Guido guys!) possesses an elegance which maybe only engineers will appreciate short-term, but which is likely to pay off in terms of the stuff folks are going to build on top of it.

Again, these guys seems to get being along the grain of the web.

Postnote: Dave Winer has a really nice short writeup on the significance of this move by Google.
Comments Permalink

More on the SSB thing

My love affair with site specific browsers has ended up a casualty of its confrontation with reality. As TechCrunch is getting ready to spin up the notion of Desktop/Web hybrid applications as the "New Old Thing," I figured it was time to point out the big hole that I did not realize until I started playing: managing security can really get you.

My interest in SSBs was borne out of two recent events: 1. that at HP there are now lots of people looking at this question of the Next Big Platform for application development and 2. that in my time here, I've also been forced to abandon Mail.app/IMAP for Gmail on the web due to all sorts of Firewall/IT complications and I've gotten tired of not having better desktop integration (drag-and-drop attachments, Ctrl-N for new messages, etc.). Figuring that I might be able both of these things from something like a Greasemonkey-enhanced Gmail, I started playing with Firefox 3 but quickly moved to Fluid due to the fact that Firefox was running like a resource pig on my Macbook. One of the apps mentioned in the TechCrunch piece cited above, Fluid does a great job of integrating a bunch of open source projects, specifically Webkit (great renderer), GreaseKit (Greasemonkey for Webkit), and Growl (desktop-level notifications). Together, I was hoping these three might let me get my drag-and-drop and keyboard shortcuts back. Or at the very least, give me a glimpse of the future of the desktop/web integration nirvana that everyone keeps theorizing about.

Unfortunately the black magic of this type of integration completely sidesteps the fact that you can quickly open up security holes worthy of trucks being driven through, especially around providing desktop-level Javascript access to the execution context of externally loaded Javascripts. In fact, even in the early days of Greasemonkey this was obvious to folks brighter than I and as a result, a whole re-architecture of the way Greasemonkey injects the local context into running web pages was needed. In the case of Greasekit however, the author felt it wiser just to pull out all of the GM_ objects that provide some of the more powerful features something that Fluid suffers as a result of.

Some of these issues can be overcome but an early brush with a big old security hole (that would give a malicious script access to my entire filesystem) got me back to thinking that we might want to wait to see how some of the big boys solve these problems. Because at least they have people whose jobs depend on not opening up huge security holes (then again, Microsoft has proven that this doesn't make a huge difference in the end).

So the romance is gone for the SSBs— at least until we a better handle on how to properly implement a security model that still exposes us to the cool guts at the intersection of the desktop and the web.

Next up: bookmarklets and AIR.

Comments Permalink

I had a wonderful time last night with Daniel Pink's new book, "The Adventures of Johnny Bunko: The Last Career Guide You'll Ever Need," not because I was looking for career advice, but because the book is written as a manga, a form of comic book popular in Japan for all sorts of ages and audiences. Apparently the author spent some time in Japan last year studying the manga industry out of which came a great Wired article that touched on some interesting points about copyright as well as the appeal of the art form in Japan.

The actual advice is very motherhood and Apple pie— don't have a plan, focus on what you are good at, focus outward instead of inward, work really hard, make smart mistakes, and try to leave a mark— but it is the story-telling that really stands out. The use of the visuals make the points of the book much more memorable (for instance, the 6 "principles" I listed above came completely from memory despite having ready this quickly late last night) and the subtle interplay between the details of art and the side comments make the overall experience really compelling.

I've long been a fan of well-written and drawn comic books. Back in the day Herge was my first English teacher, as I would take my brother's Spanish version Adventures of Tintin and read them side-by-side with my English paperback ones, thus learning English "one bubble at a time" ("blistering barnacles!" was an early favorite way to ask for things). Much later I discovered Alan Moore's incredible Watchmen (source for the best mashup ever seen here in this picture) and was absolutely blown away by how rich a story could be told in the graphic novel format (though at that critical pubescent time in my life, the prospect of getting near the opposite sex required that I read it tucked inside of my biology textbook).

And perhaps the biggest testament to the art of comics was that, back at day zero of Tabblo while I was researching what we knew about visual story-telling, my friend Jerry recommended Scott McCloud's "Understanding Comics," a wonderful book which I have referred to often over the last few years.

Even if the pundits are right and the future of the Internet is about ever richer forms of media (video, 3D worlds, etc.), Johnny Bunko is a good reminder of how much we still could learn from an old and mature art form.

Comments Permalink

So Google has finally used its offline shim, Google Gears, on the second of their apps, enabling Google Docs to make word processing offline a reality. Big single hand clap for the boys from Mountainview: we can now rely on the cloud platform to do what MacWrite did for us 24 years ago and only a year into the whole Gears thing!

I am only half-joking here. Despite the fact that this move to the cloud is probably the biggest platform shift in computing since the rise of the PC, I'm a little surprised at how the big boys' client stories are moving. For instance, Google Gears has been in beta since last summer and we've still got no support for Safari and little use inside of the Google application suite. Where is offline Gmail?

And as far as the "rich runtimes" are concerned, I remain unimpressed with the minimal offline value they bring. For example, I've been playing with a couple of the Adobe AIR Twitter clients, the best of which seems to be Twhirl, which still feels more like web widgets pasted into the desktop. In fact, the only thing I can say about all of the AIR applications I've played with is that the best of them feel like Winamp did back in the late 90s— sort of "different" for the sake of being different.

Lately, I've been thinking much more about the client side of the cloud enabling real desktop applications to make a comeback, but with the bulk of their interface being painted inside of an AJAX-enriched web browsing experience. This was why I am growing more excited about SSBs (Single Site Browsers) and also why I'm fairly intrigued by the growing popularity and portability of Webkit as a rendering engine. When combined with self-updating frameworks like Sparkle or easy Greasemonkey integration from projects like Greasekit, we might just be starting to see the outlines of the client side of cloud computing.

It's interesting to see that while the elephants are dancing in the room, we might do well to pay attention to some of the small mice scurrying about.

Comments Permalink