But, by far the best part was that you could reveal all of the formatting codes, so you could see exactly how something was styled. It was much like editing HTML by hand, and easier to figure out how something was styled than with almost any WYSIWYG.
Here’s a photo of what it looked like: https://www.reddit.com/r/GenX/comments/1aemcxc/80s_word_perf...
And it wasn't just on the DOS version. WordPerfect for Windows has/had it too along with the modern WYSIWYG UI.
GUIs are more discoverable (when done well), but DOS didn't really have a GUI option, so this was a second best. VI and emacs users sometimes print shortcut charts as well.
There weren’t any standard key combinations yet…except maybe Wordstar?… because word processors still had very very low adoption and many many users spent all day in WordPerfect so there was a lot of muscle memory.
Back then software was optimized for expertise not casual use…and priced accordingly. WordPerfect was about four hundred 1980’s dollars a seat, not 99p in an app store.
Word for Windows even had a mode that replicated the plain blue screen and behavior of WP5.1 for a few years, which I still miss.
WP also ran on the UNIX of the day, with look and feel very much like the DOS version. Tavis Ormandy got it working on Linux[0].
My more sophisticated friend had Windows 3.1 and blew my mind with the WISIWYG capabilities of early versions of Word.
Ironically, I now do much of my writing in vi.
From Almost Perfect [1], the book linked to in the article:
> WordPerfect Corporation was not a platform for personal achievement, a career ladder to other opportunities, or a challenging opportunity for personal improvement. The company did not put the needs of the individual ahead of its own. The company was not concerned about an employee's personal feelings, except as they related to the company's well-being.
> WordPerfect Corporation was not intended to be a social club for the unproductive. While other companies might condone many personal or social activities at the office, ours did not. Things like celebrating birthdays, throwing baby showers, collecting for gifts, selling Tupperware or Avon, managing sports tournaments, running betting pools, calling home to keep a romance alive or hand out chores to the children, gossiping or flirting with co-workers, getting a haircut, going to a medical or dental appointment, running to the cafeteria for a snack, coming in a little late or leaving a little early, taking Friday afternoon off, and griping about working conditions were all inappropriate when done on company time. Even though these activities were condoned by many businesses across the country, we felt there was no time for them at WordPerfect Corporation.
Sounds like a lovely place to work! Oof. Compare this to Apple or Microsoft or a ton of other Silicon Valley companies. It's no wonder they couldn't find developers:
> In January [1990] Microsoft offered to make us a beta test site for Windows 3.0. We accepted their generous offer, but did little more than look Windows over. In hindsight, it is easy to see we should have done much more right away. At the time, we could justify not doing a Windows 2.0 version in favor of completing WordPerfect 5.1 for DOS, but it is now difficult to defend our further delays. Unfortunately, we did not have any experienced Windows programmers inside the company to form a development team, and there were not many outside the company to recruit.
> In May Microsoft shipped Windows 3.0, and our worst fears became a reality. Just at the time we were decisively winning in the DOS word processing market, the personal computing world wanted Windows, bugs and all. To make matters worse, Microsoft Word for Windows was already on dealer shelves and had received good reviews. That little cloud on the horizon, which had looked so harmless in 1986, was all around us, looking ominous and threatening. IBM's strength and size were no protection. Not even an elephant could ignore the impending storm.
> May 31, 1990 was a sad day in WordPerfect Corporation's history. I wrote a press release announcing that we were postponing our OS/2 product, so we could produce a Windows version of WordPerfect as quickly as possible. I wrote, "While we still are strong supporters of OS/2, we have decided to test and release the Windows version of WordPerfect before the OS/2 version. The reasons for the schedule change have to do with the expected delays in version 2.0 of Presentation Manager and particular requests from our customers. This change should move up the release of our Windows product by three to four months and will delay our release of a PM product by four or five months."
The book is free online and pretty interesting if you like histories of early computing. It's definitely on the list with the more famous ones like Soul of a New Machine.
That's a bold statement. I think most users would disagree, and the voted with their feet/fingers, and UI designers seem to agree.
Why? Some guesses: Nothing about F# indicates what it does, making it hard to learn; ctrl+S makes sense. And after you learn it, few can touch type function keys which means, 1) you have to look away from the document and, 2) there's much less muscle memory involved.
Maybe in that way, but I think it's misleading to say a every keyboard-based non-GUI editor is essentially similar. Vi's appeal is the muscle memory of complex commands, because of the moded keyboard - one mode being character insert, the other being commands.
Didn't WP use function keys + accelerator keys? That's almost the opposite of Vi's efficiency and muscle-memory.
I don't recall any issues touch typing F-keys, either, especially on typical keyboards from that era which had the entire row split into groups of 4, making it easy to find the right key without ever looking.
I'm not sure what you mean by "much less muscle memory involved" wrt F-keys. I still, to this day, have muscle memory of F2=save from using Norton/Midnight Commander so much.
I feel like this legacy format might be the death of me. The USB is in the mail (Dad doesn't even know dropbox exists, gulp).
WordPerfect's format is a subset of Word's original.
Though, if you want to nerdsnipe yourself, the format is also documented [2], and there's a few libraries here and there for parsing it.
[1] Well, almost. The Mac-versions of WordPerfect aren't a subset of Word. See the spec docs.
[2] https://www.loc.gov/preservation/digital/formats//fdd/fdd000...
And have you ever seen (or used) one of the insane keyboards that were used to manage IBM mainframes and super-minis?
Around 2000 i found that if you have document with header/footer with auto page numbers and merge it with few pages from other document also with page numbers you get huge mess in numbering.
Some weird happens like: 1, 2, 3, 4, 5, 6, (here is doc N:2) 20, 21, 22, 23, 24, (continues doc N:1) 7, 8, 9
And you can't just reset page numbers, because you need to be on inserted page and there to do reset.
With muscle memory, you could just F2, F5, F3 combos, press tab twice and start typing [1]. The systems used were the precursor to SAP.
Function keys are really powerful. Ctrl+x works, but do these type of ctrl+letter shortcuts all day and you're guaranteed some wrist problems in a few years [2].
As a software engineer, I still put start debug on F5, end debug on F8 and used most of the other keys as well. It's interesting because that comes from my early days as a developer in DOS and then Windows. I now work on macOS though. One of the first things I change on macOS is having permanently the function keys active.
[1] arguably the main issue today is our reliance of graphical UI for repetitive work. The fact that you have to look and drag the mouse before clicking and then move your hands to your keyboard to actually type words, is insanely poor.
[2] if you're referring to the `fn` key on modern keyboard, we're then in agreeance, these are awful.
Anyway, my experience - I am in Linda's office - Linda (system manager) is not in yet, the system console is just convenient:
Me: set up job, using normal keyboard commands, with my usual login, no special privileges.
Linda: (just comes in) What you doing?
Me: Don't get your knickers in a twist. And can you make me a coffee?
Linda: Aargh! OK (we were friends), but don't press Button-B!
One of my many problems with function keys. Button-B would probably just have requested an operator to unmount a disk (or whatever), but who knows.
https://en.wikipedia.org/wiki/XyWrite
XyWrite was hardcore.
That doesn't make it a good idea. In UI design, people don't say 'we're using this because it was used in 1980s DOS programs'.
You may find it to be fine - I don't mind function keys, but I they aren't nearly as efficient. But we're talking about the general public.
Regardless, my point was that their keyboard UI wasn't as efficient as Vi. WP still made the right choice - no way the general public was learning Vi!