: User to User Support in Web Techniques. I’ve just about given up on “official” support for anything I’ll buy now. If I can’t find a good discussion group about a product or family of products, it’s unlikely that I’ll buy it. I learned how much I liked User to User support a long time ago through Apple’s and MacFixIt’s sites. But it really sunk in when I went by IBM’s site to find something out about my work-supplied ThinkPad. Uh, no. It’s practically impossible to find actual information about anything in particular. Specs? Sure. Trying to figure something out? Never.
I was a little
nonplussed by the iPod announcement at first, but there has been some very interesting commentary on Apple’s new MP3 player since Tuesday, and people are generally positive. Patrick Houston’s article from ZDNet Anchordesk, XP: Phooey on youie! Why iPod is the Apple of our eyes today, is particularly interesting.
The killer app for me, though? If the iPod could connect easily with my car CD player, I would pay the price. Maybe car stereos come with line-in ports now that I could hook to the earphone jack on the iPod. Hmmm.
A couple of days ago
Peter Merholz (of peterme.com) wrote about Zooming User Interfaces, making particular note of PAD++ implementations, which are indeed quite cool. I couldn’t help but remember Apple’s old Hotsauce project, AKA Project X. It was certainly one of the first examples of something along these lines, and interestingly enough continues to live today, in a way. For an update, visit this note by Brian Duck. It dates back to 1999 and describes how Hotsauce mutated to become part of the RDF spec.
A ton of folks
have been watching and commenting on the continuing development of Mac OS X. Unix people seem to be genuinely interested – even excited in some cases. Anyhow, today ZDNet published an interesting article in this vein: Why Apple’s bass-ackwards Unix approach is the right way.
Apple has redesigned
their Technical Note format, and altough it’s really dry information of a technical nature, in its own way it’s quite beautiful. A subdued but good use of fonts, good in-file linking that’s well distinguished from the rest of the page, a good executive summary at the top, the date of publication/update is prominently displayed, and they use shading and an indent to very clearly highlight code. And there’s a PDF equivalent available at the bottom, cause no matter how nice it looks online, a PDF will print better. Form following function, to ape the famous old line, but not devoid of form as many techies assume is appropriate for other techies.
- « Previous Page
- 1
- …
- 8
- 9
- 10
- 11
- 12
- Next Page »