#FF00AA

@misc@

Too busy working (wow, who’d have thought I’d say that again?), so I’ll be making it short and spare in the next few days.

 

@misc@

A touch-screen coffee table is anything but a new concept, but here’s a nice twist: this one is announced by HP as being commercially available by year’s end. You can throw your crappy LCD picture frames in the garbage now.

 

@apple@

So maybe the lack of a universal Adobe Photoshop is going to be a problem after all. The saddest part is, if Macromedia hadn’t been bought out, they’d have rushed to ship an optimized version of Fireworks — and maybe Adobe would have felt more pressure, too.

 

@apple@

John Gruber minimizes the OS X vulnerability and concludes:

It boils down to this: you can’t safely double-click files from untrusted sources, and you never could. This is no different today on Mac OS X 10.4 than it was a decade ago on Mac OS 8 and 9.

So, really, I was spoiled by Microsoft? I never thought I’d ever be able to say that. But, weirdly enough, if Windows tells you a file is a jpeg, then it actually is (provided you set it up to display file extensions, but doing that in OS X too doesn’t solve the problem).

On the other hand, that kind of talk isn’t too surprising coming from long-term Mac users, who have always felt, and said, that file extensions were an archaic protuberance OS X should never had grown. Well, this is a good illustration of why it’s better to use extensions than resource forks for associating files with applications: it makes the system and the internet much more safer, because every file has to ostensibly carry its identity card at all times.

 

@apple@