|
|
Wednesday, September 04, 2002
|
|
| |
Alexis Smirnov switched from a Blogger account to a Radio Blog. I'm subscribed. Today he writes:
Let’s see if I can get it straight. First of all, there’s Groove Platform. 3rd parties can develop applications on it using OEM Kit. Then, there’s Groove Workspace. It is an application that runs on top of Groove Platform, but also allows 3rd parties to extend it by writing Groove Workspace Tools.
The best analogy I can find is Windows and Office. Windows is a platform. Office is a Windows application, but you can also extend it by writing Office plug-ins and marcos.
Ok, this sounds very very reasonable and healthy. So what’s wrong with Groove’s picture? The priority. Clearly, Groove has made a conscious decision to invest much more in support for developers of Groove Workspace Tools while providing a bare minimum support for Groove Platform developers. Imagine if 95% of MSDN was allocated for information on how to develop Office plug-ins and 5% was given to help out Windows application developers. And you had to "negotiate" with Microsoft to get that 5%! [via Jeroen Bekkers' Groove Weblog]
4:33:59 PM 
|
|
The stupidest thing a software company can do. [via Krzysztof Kowalczyk's Weblog]
Nostalgia kicked in for me too. I was a die hard Commodore 64 user until the Amiga was produced, which I still believe is one of the best consumer multimedia computers to ever be built. The idea of having separate processors for audio, video and computation on the motherboard was visionary. I only wish PCs were more like this today so that I wouldn't have to pick and choose from different vendors and then worry about compatiblity problems. Yeah, I know that some people like to have the choice, but I believe that most people don't - instead they want to make sure that they are getting the most value for their money.
9:00:04 AM
|
|
|
|
© Copyright
2005
Paresh Suthar.
Last update:
8/19/2005; 3:21:58 PM.
This theme is based on the SoundWaves
(blue) Manila theme. |
|
|
