https://bz.apache.org/ooo/show_bug.cgi?id=3959
--- Comment #313 from ther <[email protected]> --- (In reply to Keith Collyer from comment #311) > > Professionally I am a requirements engineer, and I can tell you that the > last thing that most non-software developer users want is a specification in > UML ;). Use Cases are a great way of understanding and structuring > requirements, User Stories are in many ways better, but neither are > requirements. Once we have an agreed (sub-)set of user requirements, then we > can start creating the sort of detailed requirements developers need, and > designing the solution. BTW, this can be done in an agile way by identifying > the best value for least effort. > 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!". > > 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. 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". > > > As for Lyx / LaTeX, I would happily use them if I were producing documents > > > just for myself. But I work with a large team and documents are produced > > > collaboratively. Hell with be at absolute zero before they move away from > > > standard word processors. We are supposed to all use OO, but most docs are > > > still in Word. > > > > Change is painful, especially from those too old/profitable to change. > > Disruptive, innovative technology, is by definition a major threat to the > > status quo. Anyway, lyx/latex/subversion is a successful collaboration > > environment: > > https://en.wikibooks.org/wiki/LaTeX/Collaborative_Writing_of_LaTeX_Documents > > 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. -- You are receiving this mail because: You are the assignee for the issue. You are on the CC list for the issue.
