Some things just work better as a traditional app, guys.
Earlier, I wrote about how ORM developers shouldn't try to re-invent SQL . It doesn't need to be done, and you're not likely to end up with an actual improvement. SQL may be designed by committee, but it's also been refined from thousands if not millions of man-years of database experience. The same applies to DDL. (Data Definition Langage -- the part of the SQL standard that deals with CREATE and ALTER.) Unfortunately, a number of Python ORMs are trying to replace DDL with a homegrown Python API. This is a Bad Thing. There are at least four reasons why: Standards compliance Completeness Maintainability Beauty Standards compliance SQL DDL is a standard. That means if you want something more sophisticated than Emacs, you can choose any of half a dozen modeling tools like ERwin or ER/Studio to generate and edit your DDL. The Python data definition APIs, by contrast, aren't even compatibile with other Python tools. You can't take a table definition
Comments
The thing that concerned me about Meebo is security. Do I want to give them my yahoo id and password?
(But it might be nice if you need IM and you are at a random machine that happens to have a recent browser (and no IM client))
Of course, you'd already have logged in using your Passport account, so the trust issue isn't there in quite the same way.
I think that this is something that works pretty well in an AJAX context (although it's not as nicely unobtrusive as a desktop client). (Well, some messaging clients.)
I was marginally floored (I mean, I'm told I've done something similar in the past, but that's cool). Meebo certainly has its uses (a locked down windows lab in the EE dept with no software installation allowed, for example).
My friend's response was "holy cow, isn't that a privacy concern?"
useful, marginally.
worth building a business around... no.
Maybe this is a resume builder? I doubt they're hoping to be bought.