Comment Re:TeX for Math (Score 1) 300
One of the other advantages for the troff approach at that time was version control -- the documentation folks could use the same system that the coders used.
...no distractions while edition (MS GUIs suck)...
At some point there was an internal study at Bell Labs
after WYSIWYG word processors were beginning to be available
that found most people spent 20% of their time
futzing with how the document looked instead of writing.
Most of that time was wasted because subsequent changes were
going to wipe out whatever the little tweaks had been intended to accomplish.
Interesting that today you can buy programs
whose primary purpose is to blank all of your display except for
a green-on-black mono-spaced text window.
Sold as an aid for professional writers who need to pound out
umpteen pages of text per day,
so need to avoid interruptions and distractions while composing.
I can't really explain it other than to say "you get used to it." After a while, the markup becomes transparent...
Just like learning any other language, I suppose. Years ago I had a guy working for me who could do it with troff's pic preprocessor. He could "draw" lovely semi-technical diagrams of various sorts writing text in an editor in one window with a second window set up to render it when he clicked the mouse there. It didn't hurt that he had accumulated a whole library of code for drawing various shapes that he used frequently.
That is a way around the "problem" for the publishers.
Particularly when they convince the schools to include the e-book license fee as part of the cost of the class. "We don't care where you download the copy, we get paid regardless."
Having a real-time chat for office hours is a nice shiny toy, but it's not really useful for demonstrations or sketches.
One of my larger disappointments is the lack of good readily-available free multimedia conferencing. Checking my old lab notebooks, it's been a few months short of 20 years since I built multiple sets of prototype software for doing real-time audio, video, and a shared piece of paper over IP networks. When I was doing that, I really expected that within a decade we would have appropriate inexpensive I/O devices to make the paper part truly useful -- trying to write calculus equations or sketch a curve quickly really needs the feedback of a stylus on a surface where the drawing is visible under the stylus tip. And I expected IP multicast to be readily available, which helps a lot with multi-point distribution of the audio and video. I had real people at locations as far apart as Denver and Minneapolis using a version of the software very effectively over our corporate network, mostly sans video because there wasn't enough bandwidth. One of those users came to get me the day they were running a seven-way conversation using three copies of the application to give them three simultaneous sheets of paper (mostly cutting and pasting pieces of screen shots, then marking them up, with a record of the session going into a file). I thought, "Man, this is going to make a bunch of things a lot quicker and easier." Starting with office hours.
Like I said, one of the bigger disappoints in my technical career.
IE fiasco? Are you talking about the same "fiasco" where IE ended up with around 95% marketshare? Sounds like a raging success to me.
The same fiasco where, absent George W. Bush beating Al Gore (a result that would almost certainly have gone the other way if Ralph Nader had not been on the ballot in Florida and taken 3% of the vote) and changing the direction of the Justice Department, MS winds up as two companies -- an OS company and an application company, forbidden from cooperating. A business strategy that comes within an eyelash of getting your company broken up by the anti-trust people is a fiasco for management, at least IMO.
"Remember, extremism in the nondefense of moderation is not a virtue." -- Peter Neumann, about usenet