...more recent posts
Buttress "is a broadcatching application to automatically download and run .torrent files from RSS feeds, without user input." This is what I want, but unfortunately I can't get it to work yet on OS X. I think it should though, not sure what I am doing wrong. It scans the RSS feeds okay, but then complains that it can't start up my Bit Torrent client.
The Buttress download contains an .exe file for windows users. Unix people should be able to run the .jar java file, although like I said I haven't been totally successful yet on OS X. I'll comment below if I ever get it working. Windows users may want to give it a look.
Wow. Technorati This favelet/bookmarklet. Handy.
Russel Beatie continues to make his case that mobile handsets are where the action is:
Apple shipped 4 million iPods in the past quarter, Palm shipped 1.5 million Treos and Dell shipped 8 million PCs..... Very nice, but Nokia shipped over 50 million handsets in the same timeframe.
The good folks at Downhill Battle have released Blog Torrent, a PHP project that simplifies offering Bit Torrent downloads from your PHP enabled website.
[W]hat blogtorrent does is give users "easy download" links in addition to links to the torrent files. The "easy download" link gives them the torrent file they want wrapped in an executable installer. The installer just installs Bittorrent, asks them where to save the file, and starts getting the torrent they want.This isn't brain surgery. It's just installing the Bit Torrent client invisibly when (windows users, for now) click on the download link. But even though that isn't much (can't people install the client themselves? Well, sometimes not...) it should help. And it makes uploading Torrents easier too. Something to watch for sure.
Internal IBM interview with John McCalpin: On the POWER7, Simultaneous Multi-Threading - and the true origins of AIX. (via HTP)
POWER7? Good God these guys plan ahead (POWER5 is the cutting edge at the moment, while Apple's G5 is a simplified version of the POWER4.) Super geeky, but interesting if you are into such things. I love the "Level: Introductory" label applied to the article. Yeah, "introductory" if you are a hardware engineer working for IBM.
Also liked this exchange:
dW: That is a shame. I have one more on the subject of OSes -- was AIX really designed by space aliens?Hmmm. Classic non-denial denial? The truth is out there.
McCalpin: I hadn't heard that one....
KISS: Keep It Simple and Sloppy.
Adam Bosworth has been writing some interesting posts lately. He used to work at Microsoft where he was responsible for developing Microsoft Access PC Database, the HTML engine for Internet Explorer 4 and 5, as well as directing most of their XML development work from 1997 to 1999. He later worked as Chief Architect and Senior Vice President of Advanced Development at BEA Systems. And he now works at Google. (Slightly out of date bio link.) In other words, he knows a few things!
He recently spoke at the 2nd International Conference on
Service Oriented Computing (ICSOC04,) and reprinted his speech on his weblog. It's long but very interesting. Well, okay, interesting to me at least. He is able to look at where the web is going from a very high altitude without losing touch with the finer details of implementation.
If you think about web architecture you should read this piece. It is basically the same as my philosophy of how to build things, except I'm not so smart or experienced (understatement of the year) to have put it as well as he has.
The Treo 650 is on sale now directly from Sprint (warning: link to very dorky treo message board.) Might possibly be only available to current Sprint customers (there is some mixed experiences here.) $599 with $150 rebate for Sprint customers of 18 months or longer.
Okay, this phone rocks. The question is: does it make any sense at all to buy such an expensive mobile device when it can't be used on any of the new high speed wireless networks?
Mobileburn has an article, with lots of pictures, comparing the output of some 1 megapixel camera phones. The phones are the Sony Ericsson S700i, the Siemens S65, and the Motorola V710, with some extra shots from the Nokia 7610 and the Sharp GX30 thrown in at the end.
The Motorola definitely proves that more pixels don't always equal good pictures. The others do a pretty good job though. The S700 seems particularly good. Of course now I can't wait for the 2 megapixel untis shipping in the 2nd half of 2005.
I have been eagerly awaiting the debut of the Treo 650 cellphone. It has been officially announced, but isn't on sale yet. The big disappointment with the specs is that the camera did not increase in resolution. It's still just a VGA (about 1/3 of a megapixel.) When I first heard this I thought it was a deal breaker and I started to look for other possible phones (more on that later,) but now I am not so sure. It may turn out that the sheer number of pixels the camera can resolve is not the only factor.
Palm (who makes the Treo,) said they had planned to include a 1+ megapixel sensor, but could not find one that operated well in low light conditions. As the owner of a Treo 600, I can say that this was that cameras greatest failing. It is basically useless when not in bright sunlight. So Palm stuck with the VGA sensor, but they say it is different, and that the second generation VGA sensors, combined with a new lens, and new software, make for a better camera than the first generation 1 megapixel sensors that are out now.
Here are some side by side comparisons of pictures from the 600 and 650. It really does seem much improved. And the 650 shoots very small videos as well.
Now I am back to undecided. Certainly seems very usable.
Still working on the new layout. Not that I care too much, but I am trying to use my page to learn non table based CSS design. I made something I really liked, but then it turns out that it is completely borked in IE. So I dropped back to this non-design for the moment.
This is the madness of designing for browsers. It's not as bad as it used to be (specifically because you can safely forget about the hell that was Navigator 4,) but it is still a pain. For anything but the most simple design you probably have to do some browser sniffing and serve up different CSS files for different browsers/platforms. That is a change I had sort of wanted to make anyway (putting the CSS into a separate file rather than including it inline,) but it will be a slightly more involved operation to do it this way.
Yeah, I know, pretty interesting...