Names are really important. This is a bad name. Gimp, the image editor, is another victim of OSS naming. I know many serious artists who won't give it a try si

Names are really important. This is a bad name. Gimp, the image editor, is another victim of OSS naming. I know many serious artists who won't give it a try simply because of the name. They don't take it seriously. The fact that it's free is unimportant to them. With a better name a decade ago, Gimp could be a serious competitor to Photoshop now, instead of a footnote. In this case, the developers are putting a clumsy emphasis on the price and "freedom", which is unimportant to someone who just wants to write a letter or make a presentation. Read "LibreOffice" literally .. "A free alternative to MS Office". Which is not untrue but this immediately raises the question "Can you afford the REAL MS Office? And are you worth it?" Most people will answer, "Yes, I can and I am certainly worth it". Starving students may answer "No, but it's less work to pirate it than to install this weird thing." My belief is that for an OSS office suite to dethrone MS Office, it needs a clear focus, and one other than "free". Brainstorming some directions they could have taken: LessOffice - A streamlined office suite, fast and bloat-free, that never crashes. (Of course, OpenOffice is pretty far from this in reality) CopyDesk - A word processor for writers, not for bureaucrats. DeFacto - An office suite that interoperates seamlessly with every other system. It never asks what format something is in, it just works. BloatOffice - Has every feature from every other office suite. Combined. The most complete office suite on the planet. (A bit self-deprecating, but could turn a perceived weakness, bloat, into a feature, completeness). Folio - An office suite without the learning curve. In any case, this market is long overdue to be disrupted. Google Docs isn't going to do it. I'm a writer, and I can't even get it to do proper manuscript format. A typewriter can do that. Developers: If you REALLY want to help the free software movement break MS's stranglehold on Office, don't write another office suite. Write a self-contained, standalone library that reads and writes .doc files, that works perfectly for the features it supports and clearly indicates to the caller when it's going to break and what it's breaking on. Once you can write a 200 line example program that converts most docs to nearly identical .pdfs, you've won. Not that that's easy.