Some things just work better as a traditional app, guys.
At my day job, I write code for a company called Berkeley Data Systems. (They found me through this blog, actually. It's been a good place to work.) Our first product is free online backup at mozy.com . Our second beta release was yesterday; the obvious problems have been fixed, so I feel reasonably good about blogging about it. Our back end, which is the most algorithmically complex part -- as opposed to fighting-Microsoft-APIs complex, as we have to in our desktop client -- is 90% in python with one C extension for speed. We (well, they, since I wasn't at the company at that point) initially chose Python for speed of development, and it's definitely fulfilled that expectation. (It's also lived up to its reputation for readability, in that the Python code has had 3 different developers -- in serial -- with very quick ramp-ups in each case. Python's succinctness and and one-obvious-way-to-do-it philosophy played a big part in this.) If you try it out, pleas
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.