Challenging Microsoft on the Desktop
Dotnaught writes "As Microsoft moves to offer software-as-a-service with Windows Live, online companies are moving to challenge Microsoft on the desktop. In a decision that would have been seen as foolish a few years ago, file sharing and social networking company TransMedia plans to release desktop productivity apps (in conjunction with online ones) as lightweight Microsoft Office alternatives. Google, meanwhile, through its deal with Intuit, is colonizing desktop apps as it has done with browsers and search toolbars. Microsoft used to have a home field advantage on the desktop, thanks to Windows. Lately, operating system ownership is looking a lot less valuable."
There is not a chance in hell I would use an online app for something that runs fine on my local pc. Why add an unneeded security risk?
>>Lately, operating system ownership is looking a lot less valuable.
This could not have been true-er. First, I substituted MS Office with OpenOffice*. After Google came out with spreadsheet and document solutions of its own, I do not even use OpenOffice anymore. What more, it does not matter anymore if I am on Windows XP or Ubuntu or Suse - as long as I have a relatively mainsteam browser with me, I am good to go.
*I am talking about my home environment where I do not user "Office" applications that heavily, and online solutions available to me satisfy ALL my needs.
Many vendors could easily out-do MSFT in application space. MSFT did not get its marketshare and lead by simple technical superiority of its product or coding skills. It got it by better business tactics. Infact every flag ship product that is minting money for MSFT started out as a pale copy of some other better program. WordPerfect, QuattroPro/Lotus, Harvard Presentation Graphics, Dbase/Foxbase etc. Then the marketing muscle, clever tricks to prevent interoperability, agreements with vendors to throttle competition and naivity of its user base that confused interoperability with PC-compatibility got MSFT the market share and lead. If the OS advantage is removed and the playing field is leveled by demanding true interoperability and compatibility to standards, (standards not wholly owned and manipulated by MSFT) you will see what other vendors are truly capable of.
The key is Open STANDARDS. Do not confuse it with Linux/Mac/Unix or Open Source or Free Software or Gnu or GPL. If the users demand true portability of their data and their applications the playing field will be leveled. My docment, my macros, my scripts are mine. I want them to work whether I choose to run MSOffice or OpenOffice. Only when owners of the data assert their ownership and refuse to be locked into a particular vendor's format the playing field will be level.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
"OO Writer tries to do everything on all platforms, and it became heavily bloated"
What about Abiword?
I'd prefer FCKEditor on a simple web page than OO Writer. OO Writer tries to do everything on all platforms, and it became heavily bloated.
I don't mind OO writer, but I can see where others might. One thing I'd like to see that might help mitigate that kind of bloat is something like the system services on OS X. They've added spell checking and a dictionary/thesaurus that can be accessed by any application and a grammar checker is supposed to be built into Leopard. I also use a more comprehensive collection of online dictionaries, some macros and scripts, quick language translations, automated bibliography citations, and statistic summaries (word/page count etc.) on a regular basis. Since they are implemented as services rather than built into every program, I can add them or not add them for a given program without any bloat and build up a custom toolbox with just the features I need. Don't need a quick translation to/from german? Don't add it to your services. This sort of customizability goes a long way towards removing the bloat while still letting any given user have the features they want or need and keeps you from having to rely on multiple implementations of the same thing for different programs (I taught my dictionary that ICMP is not a misspelling in InDesign... I don't want to have to do the same in Vi, Pico, Word, TextEdit, Photoshop, Safari, etc.).
The bad reputation they would create would kill them commercially.
And lets not even mention lawsuits.
Well, what the heck, lets do it: lawsuits.
IANAL but write like a drunk one.