AjaxWrite

Posted on March 23, 2006
Filed Under Innovation |

Lot's of blog postings about AjaxWrite today. I tried the service:

1) It ain't a word processor, it's a text editor. Which is all well and good if you want to do simple editing, but comparing it to Word and Writely does a disservice to all of the products. On one hand it sets up ajaxwrite to be a big disappointment, while on the other hand it diminishes the significant feature sets that the other products feature.

Critics of MS Word like to say "yeah but I never use all of the features in Word" and that's a fair point, but the reason it's not called "Jeff's Word Processor" is that there are people who do use the features that I don't. I never used table of contents, but my assistant did and without it she would have faced a big challenge. Over time even Microsoft will evolve to a services based application architecture where I get to pick and choose what features I need, but nobody really has that today to the level of sophistication that these applications represent.

Ajaxwrite-1

2) Secondly, ajaxwrite didn't work very well for me. The server was largely unavailable and loading the app caused my browser to reset several times. Can you imagine using this service for critical documents and facing that kind of reliability challenge? No.

Technorati Tags: ajaxwrite, microsoft, web2, writely

Comments

  • Feeds