Skip to main content

Mac OS X Dashboard - Haven't I seen This Before?

I'll give Apple heavy kudos on this - they have managed to take something that other OS's have done and turn it into a very "cool" looking demo. The Dashboard is a "home to widgets", tools that let you perform common tasks and provide fast access to information.

Ummm....yes, Microsoft had something called the Digital Dashboard
but that was more about data.

Apple's demo of the Dashboard actually reminds me more of the "Active Desktop" (now, come on - be serious - how many of you still use the Active Desktop? - when I search for Active Desktop on the the MS web site, it takes me to a "The page you are looking for has been removed" but here's a link to a recent (well semi-recent) article. The description from Microsoft:

The Active Desktop interface lets you put "active content" from Web pages onto your desktop. For example, you could put a constantly updating stock ticker in a handy place on your desktop or make your favorite online newspaper your desktop wallpaper. You can make your desktop truly your own space by adding the active items you need to refer to on a regular basis: news, weather, sports, stock prices, or whatever you want to have at hand. Your desktop can now reflect you--your preferences and your style.

Kind of sounds the same? Wonder if the fate will be the same. I recall when it first came out, many end users turned it on only to have their IT people run around turning it off because it confused them so much. Hopefully Apple users will have a better experience (they typically do)

Yes, the Apple demo really does look very cool but as Ars Technico notes : You can probably guess that those special effects won't work on every Mac out there.

Apple - Mac OS X - Theater - Dashboard

Comments

Ted Roche said…
IIRC, there are some innovations here over what was possible with MS' Active Desktop, but Apple's widgets are disturbingly similar to a 3rd party product - see http://daringfireball.net/2004/06/dashboard_vs_konfabulator. There is a contingent within the Apple community that protests that anything they do - Sherlock vs. Watson, Spotlight vs. Google Desktop Seach, etc. are all rip-offs. Hard to tell. We don't, after all, want anyone to be able to patent an idea and lock it away from the rest of us.

A wise man (or was he a wise guy?) once said that there are only 23 problems in computing. And we keep solving them over and over...

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...