https://bz.apache.org/ooo/show_bug.cgi?id=3959
--- Comment #317 from Keith Collyer <[email protected]> --- (In reply to ther from comment #313) > (In reply to Keith Collyer from comment #311) > > [snip] > The m$-clone fans do not seem prepared to acknowledge the difficulty of the > task. After all these years, there does not seem to be a definitive > specification, except for "I do this in m$, make it happen in oo at once!". Please stop your childish "m$" nonsense, that was funny twenty years ago, it is just pathetic now. Nobody is denying it will be difficult. Nobody is expecting it to happen just because they want it. I made a start on stating requirements, feel free to add to it. > > As for the Unix mindset, that is a valid point, though it isn't a mindset > > that is acceptable to most word processor users. If OO is to be seen as a > > credible alternative to MS Office, it has to be acceptable to those who have > > grown up using MS. That is just reality. Refusing to see that means that OO > > will remain like Linux, in many ways better than the MS alternative, but > > never reaching mass appeal. > > > > Disagree with the "grown up with m$" excuse. Globally, there is a generation > of IT users whose first experience will be via (gnu/linux android!) mobile > phone. Not an excuse, a fact. Some of us have to live in the real world. And as for Android being based on Linux, oh, please! Nobody outside us geeks even knows or cares that it is. They certainly don't see it in the UI. There is nothing in a standard Android distribution that is visible to a normal user as Unix-based. And how many people try to use office tools on a phone anyway? I know you can, I have more than one office suite installed on my phone and my tablet. But it isn't mass market. > OO does not need to reach mass appeal immediately by being a m$ clone. A > better long term strategy is to focus on superior features that justify a > change, not "oo is a free m$-clone, you can change today without learning > anything new". Right, so help to specify and create an outliner that is better than Word. I already gave a couple of examples in the requirements I added. Having used both tools extensively, it is difficult to think of a feature that I have used where one is significantly better than the other - except for outlining. So the long-term strategy isn't working - yet. [snip] > > I didn't say it couldn't be done, I said it would not happen. And where I > > work is fairly typical of most organizations. Even the geeks and nerds among > > us aren't geeky or nerdy enough to go against the flow and make our lives > > unnecessarily difficult. Read my earlier comments, I used to write Lisp > > professionally in EMACS, you don't get much more nerdy than that. > > Don't be too dismissive; having witnessed such a change, it can and does > happen. Trust me on this, it won't happen, not where I work. -- You are receiving this mail because: You are the assignee for the issue. You are on the CC list for the issue.
