At the risk of beating a horse to death, today I stumbled on an online
rant against MS-Word.
http://www.antipope.org/charlie/blog-static/2013/10/why-microsoft-word-must-die.html
While the entire blog is worth reading, I was particularly struck by the
following, which describes precisely my frustration with the design of
the "one size fits all" office word processor.
"Steve Jobs approached Bill Gates to write applications for the new
Macintosh system in 1984, and Bill agreed. One of his first jobs was to
organize the first true WYSIWYG word processor for a personal computer
-- Microsoft Word for Macintosh. Arguments raged internally: should it
use control codes, or hierarchical style sheets? In the end, the decree
went out: Word should implement /both/ formatting paradigms. Even though
they're fundamentally incompatible and you can get into a horrible mess
by applying simple character formatting to a style-driven document, or
vice versa. Word was in fact broken by design, from the outset -- and it
only got worse from there."
Virgil
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] direct formatting and styles · Virgil Arrington
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.