macidiot said:
I'll second that!
I still use Watson today.
The biggest problem with Sherlock was that it was Carbon and a pain to develop tools for. On the other hand, Watson was Cocoa and was designed to be easy to create tools for.
The idea behind Watson (that Apple never got with sherlock) was that Watson was supposed to be a development environment for creating web services. Rather than making a stand alone web service app (like OmniDictionary for example), you could make a tool that ran within Watson. Because web services scrub information from web sites, and many web sites change their layout regularly, the stand alone application setup requires more work on both the part of the developer and the end user. With Watson (before Sun bought it) when a tool broke, the developer could fix the tool without the application (Watson) itself having to be replaced.
Had Apple understood the true power of Watson... and either bought Watson out right or
really made Sherlock in Watson's image, they would have been pushing something like Watson with WebObjects.
The biggest problem with web (browser) based applications is that it is really easy to leave the page you were working in (basically the same reason some companies were so upset when Microsoft made Internet Explorer part of the OS in Windows 98) to go browse the net. But if you developed an interface for your WebObjects app as a tool in Watson, then it feels like you are using an application on your system rather than via a page in a browser.
Will Apple ever get this?. No.
They've moved on to Dashboard. And while building widgets for Dashboard is easier than both Sherlock and Watson, Dashboard widgets don't provide the same type of professional interface as a real app, nor are they as easy to work with for extended periods as real apps.