Skip to main content

When all you have is a hammer....

Everything looks like a nail.

Some things just work better as a traditional app, guys.

Comments

Anonymous said…
A friend and I have recently been feuding over AJAX, and whether it will cause the end of the desktop. I think a lot of things can go to AJAX (and others can't).

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))
Anonymous said…
Microsoft has had an AJAXy web-based MS Messenger client (IE only, of course) for at least a year.

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.)
Anonymous said…
You didn't think that was pretty cool?
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?"
Jonathan Ellis said…
cool, yes.

useful, marginally.

worth building a business around... no.
Anonymous said…
Agreed, though nowhere can I find anything about their business model, if any, or how they plan to make money.

Maybe this is a resume builder? I doubt they're hoping to be bought.

Popular posts from this blog

A week of Windows Subsystem for Linux

I first experimented with WSL2 as a daily development environment two years ago. Things were still pretty rough around the edges, especially with JetBrains' IDEs, and I ended up buying a dedicated Linux workstation so I wouldn't have to deal with the pain.  Unfortunately, the Linux box developed a heat management problem, and simultaneously I found myself needing a beefier GPU than it had for working on multi-vector encoding , so I decided to give WSL2 another try. Here's some of the highlights and lowlights. TLDR, it's working well enough that I'm probably going to continue using it as my primary development machine going forward. The Good NVIDIA CUDA drivers just work. I was blown away that I ran conda install cuda -c nvidia and it worked the first try. No farting around with Linux kernel header versions or arcane errors from nvidia-smi. It just worked, including with PyTorch. JetBrains products work a lot better now in remote development mod...

Python at Mozy.com

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...

Why PHP sucks

(July 8 2005) Apparently I got linked by some PHP sites, and while there were a few well-reasoned comments here I mostly just got people who only knew PHP reacting like I told them their firstborn was ugly. These people tended to give variants on one or more themes: All environments have warts, so PHP is no worse than anything else in this respect I can work around PHP's problems, ergo they are not really problems You aren't experienced enough in PHP to judge it yet As to the first, it is true that PHP is not alone in having warts. However, the lack of qualitative difference does not mean that the quantitative difference is insignificant. Similarly, problems can be worked around, but languages/environments designed by people with more foresight and, to put it bluntly, clue, simply don't make the kind of really boneheaded architecture mistakes that you can't help but run into on a daily baisis in PHP. Finally, as I noted in my original introduction, with PHP, ...