Word has version control though, and it's appreciated by many in academia. Version control for humans is a Big Startup Idea, I wouldn't be surprised if Dropbox and Github were trying to tackle it (from 2 different angles: Dropbox from the "how do we get average the user to get features for nerds", and Github from the "how do we get the average non-nerd to use us")
Word's review functions appear as pretty colored bubbles and a bunch of icons on the Ribbon. It's easy enough even for Humanities professors to use on a daily basis, despite the fact that as a VCS, it's strictly inferior to something like git. Actually, I think it's popular precisely because it ain't git. Most professors who are fluent in Word's review functions would be hopelessly lost when faced with a Dropbox conflict, let alone merging git repos.
As for git's complexity, it's all in its completely opaque display of its internal state. A chain of deltas - diffs - isn't complicated. It's all git's (perverse) desire to follow the exact-same command-line interface as cat and awk, when neither contain persistent state.
Word shows pretty bubbles next to sections that have been edited. The bubbles are color-coded so it's easy to tell who did what. The edits can be accepted, rejected, or further modified with a couple of clicks. There is no list of commands or keyboard shortcuts to memorize. Just a bunch of icons, menus, and clicking around.
Word doesn't require your content to be made up of neat lines of verse, either. Natural languages don't organize themselves into 78-char lines. It should be OK to edit a few words in a long paragraph of prose. Even Wikipedia's messy "Revision History" is probably better than git in this regard.
It is a horrible representation for stuff where edits may consist of both typo fixes, and separate wording changes in a single sentence - where you might want to accept change to one word and reject change to another word, despite that they came from a single "commit" to a single line.
For collaborative text editing both word's track changes and google docs features are far superior to git.
We're bringing version control to people who collaborate by email, starting with Gmail. All people have to do is exchange drafts by email (like normal!), and we infer the history, as if they've been using git.
We're looking for beta testers:
https://draftable.com/gmail/faq
with the answer to your question (and more), but I'll answer here too:
We don't modify the data in your Gmail account, so if you try Draftable, then uninstall it, your Gmail account won't be altered. Furthermore, if you disable Draftable before uninstalling it, we'll delete our index and revoke our access to your account.
It's meant for people who exchange documents by email.
Collaboration in physics research: hand-written notes on margins of said pile
The issue with git etc is that everyone involved has to understand how it works and accept and appreciate the benefits over the system outlined above (which works quite well for papers with few authors). If even one author doesn't care, you cannot implement the system. And good luck getting professors to care about things that aren't research or funding.
And if some of them can't use it, teach them. And revert to the previously non-fucked up version (it's on someone's email by the name of Article_1_fixed_2_corrections_10_10.docx)
Something I like about version control is that it at least ensures continuity of the version.
Yours sincerely, a graduate student whose thesis is written in LaTeX and then converted to RTF and then hand edited so his supervisor(s) can give him comments.
I sent them a link to my github repository, but they never took me up on my offer :(
I've found that collaboration on documents via Markdown is not too crazy bad. Otherwise, I ask for comments on the PDF or on hard copy. Going back to latex from RTF is an exercise in madness.
And I second the pandoc recommendation if you can get it to work
The worst part was that they didn't even use the track changes feature on anything I sent them.
I actually do make bit of things in LaTeX through Org-mode at the office, and sending things in PDF actually makes it clear what kind of handling I'm looking for. If I'm actually expecting someone to revise my writing, then I'll just send them plaintext.
Now considering even Adobe Reader allows commenting, I don't think there are many of issues any more...
I don't know the state of visual tools for git but tortoisehg for mercurial is quite easy to get started with.
After forgetting to push after commit and then dropping your laptop, you'll know.
Nope, like regularfry rightly pointed out.
>The only difference is that you still can use your local git repository if your server burns down, but you can't do that with svn. Even then I can `svn relocate`.
Look, I am not defending SVN for software development, I am a happy git camper. But git for technical writing is simply the wrong tool for the wrong job.
I have had various beginner git users get very confused when dealing with conflicts -- I have got myself quite confused on occasion too.
1. http://www.wired.com/wiredenterprise/2013/06/cades-witty-hea...
Mostly because he was drugged, physically and psychologically tortured and reduced to his basic instinct and given option to experience its greatest fear or 'love' Big Brother. That's closer to real world than it being the only good option. LibreOffice needs a good compare function, not the whole review shtick.
Sounds remarkably like using Microsoft Office.
Basically, you pulled this out of your butt because it hit the right notes and because it fit the preconceived notions of the readership of HN. WYSIWYG word processing was actually pioneered at Xerox PARC and MS Word has a direct lineage from there. Fitting the office correspondence conventions of the time was the obvious place to start. In a world that still operates off of paper, this is what makes sense at first.
Java classes like EnterpriseBusinessInterconnectInterfaceFactoryFactoryFactory are a direct result of the deliberate crippling of the Smalltalk runtime model that Java was based on. The very small and minimalist Smalltalk runtime model was another product of Xerox PARC, BTW.
Back in the day, even Java was one of these subversive back-door hacker/engineer things management wasn't hip enough to be a part of. (Unless you were one of the even hipper folks into Smalltalk, Dylan, Common Lisp, Eiffel, Tcl/Tk, Perl, Python, what have you, in which case, you knew better than to fall for Java.)
Heck even SQL, Fortran, and COBOL were the new hip thing back in the day. (Even if that came with corporate backing.)
Actually, they are a consequence how easy Java allows to write such type of code and how enterprise architects design software.
I have seen EnterpriseBusinessInterconnectInterfaceFactoryFactoryFactory examples in the enterprise done in lots of languages.
The same way there are developers that write FORTRAN in any language, there are those that make Skyscrapper designs in any language.
Then indeed, its influence over those fields should be allowed to wane.
LibreOffice? Call me again when it gets the Review function right.
I was required to use the Review feature as a sort of half-assed collaborative editing system for tech specs on a couple of projects around 2008-2010. I found it to be a buggy, work-destroying trap of a feature. Things would actually have gone more smoothly for my project Microsoft had never implemented this feature.
I haven't tried any similar features in LibreOffice. If it doesn't do anything totally crazy (like randomly duplicating blocks of text in odd places) it's probably better.
I read an interview with some high-muckety-muck in the MS Office group years ago. He actually said, in response to a question about features vs. bug fixes, that he was sure users preferred new features to bug fixes for old ones. That features got people excited and no one really cared if they lost a little work every few hours.
He didn't say he'd asked any users. He was just sure.
I wish I could link to it, but I don't recall where I read it.
He's probably right (if you think of users as being the person who approves the payment). I can't imagine the CFO at a Fortune 500 company approving a few million dollars to be spent on bug fixes. The obvious question would be "why did we pay for defective software in the first place?".
So perhaps one side effect of the subscription model will be less buggy software, since the business model relies more on keeping users than getting them to upgrade.
Don't bastardize the message and theme of the book.
IGNORANCE IS STRENGTH.That's Abiword. A much smaller and cheaper piece of software.
That is all that most office workers need. So why is Office, a huge piece of software the default?
Abiword's grammar checker is not nearly as good as Word's. That is specially in non-english laguanges. Also I would add to that list all the templates and design that Word brings out-of-box.
I am a weird case because I use Abiword at work and Office at home. And at least for short documents (10 pages max.) the experience on Word is just more enjoyable to me.
From a linguist's point of view, the language that English is grammar checked against in Word has always been a broken approximation of an uninformed prescriptivist's version of English.
An example opinion from the guy who wrote the book on English grammar:
http://itre.cis.upenn.edu/~myl/languagelog/archives/005061.h...
I have actually only used one working spell checker for Swedish: stava. And the ideas behind it are trivial, so I guess that nobody else has written a specialized spell checker for Swedish. Generalized ones like ispell, aspell, hunspell and Word's do not work for Swedish.
LOL seriously? Look everybody, v2 even has footnotes and -gasp- tables! And they are 'very powerful' tables, too, because you can even merge cells (in a 'non-modal dialog', no less!)
(oh, and last release version - 2009).
Most users don't care so much about the "size" so much as the cost.
You both got it wrong. It's not about size. Not about cost. It's about compatibility. People use word because their boss, publisher, or professor uses word. Because an entire ecosystem of office software integrates in word. Because kids taking a computer class in school learn Word commands, and nothing else. Because a perfectly styled document in LibreOffice doesn't always look right in Word.
More than 20 years later, Microsoft still survives off the popularity of DOS on IBM compatible pc's in the late 80s and early 90s. Their strategy since has been to further entrench themselves into our daily lives.
I suspect this is the ultimate longevity of Word. Retraining is a real pain. So the only way to kill Word is by a thousand cuts. One of those cuts seems to be Google's documents. A number of non-technical folks can now send me a document in Google Docs so I don't have to switch from my Linux desktop to something else to access it, and Google has done a reasonable job of auto importing Word.
So domain specific solutions, with "good enough" import/export may be the solution.
Unfortunately as Publishing is now having to deal with online and electronic it means they are not best placed to deal with the changes.
And book publishers have sclerotic processes (makes teh Laudry service seem slick and efficient) to take a book from delivery to publication and extra month or so playing with word is't going to make much difference
And that's why they released a "Home and Student Edition".
Student Edition: "Give them Office now at a discount, and they'll keep using (more expensive versions of) Office when they get a real job."
Office is named Office for a reason. Its entire existence revolves around the typical 20th-century white-collar office. All other use cases are secondary.
Just a thought.
They prohibit you from making money with it? That blows my mind. Not only is it completely unenforceable (the PR backlash from Microsoft doing an enforced license audit of the likely purchaser of that version would be immense), it's completely pointless. Again, the products are differentiated by what they lack.
I wonder if the Microsoft legal department counts creating lemonade stand or yard sale signage to be "commercial use"...
However, I don't think there's a way to upgrade if you buy Home & Student and then discover that you need to do commercial work with it. You have to buy a new license.
By the way, Windows includes a free word processor, WordPad, that does what most home users need without them having to buy Office. There are also free viewers for Office docs...
Microsoft Office is commercial software costs roughly $300. If you want to use it for commercial purposes, you pay the price. However, there's a special deal where you get a Home & Student version for a third of the price, on condition that you don't use it for commercial purposes (ie as a replacement for the version you should be buying).
A lot of commercial programs are available in cheap student versions or in free versions for home (non-commercial) use. This is standard industry practice. It's not a Microsoft thing.
Confluence? Twiki? Or equal such centralised documentaiotn and revision service, be it SaaS or locally hosted, Yes.
He pointed that out. And he pointed out that the industry was still foisting it on him. That is why he wants it to die. This was the summary at the end of the article in fact.
I don't think most people distinguish "Word" docs from any printed doc, except those sophisticated enough to use "Excel" to produce columnar-format data ("Word" tables are hard to do and sucky looking).
Microsoft Word was never designed to be an ideal tool for creative writing, programming, or any such thing. It was designed to help office workers produce business documents (a) quickly, (b) in a format that integrates with all the other programs in the Office suite, and (b) in conformance with whatever formatting and workflow requirements their employer already had in place. Microsoft probably consulted with a bunch of Big Business customers when they designed Office. Yep, the kind of Big Business that uses Java classes like EnterpriseBusinessInterconnectInterfaceFactoryFactoryFactory.
Type a few word, hit "Save", and automatically get reasonable default fonts and margins? Check. Type a few more words, make some typos, have them fixed automatically? Check. Certain words need to be italicized or underlined? Check. Certain words need to be in a different font? Check. Who cares if it's consistent, the boss wants it bold so just make it bold. Indent the first line by X inches, double-space here, single-space there? Check. All accomplished with a few clicks of the mouse. No need to learn any command-line programs, formatting \Syn\{TaX}, or keyboard shortcuts. It's exactly what the majority of office workers need. Bonus points if it also helps clueless parents design their daughter's birthday party flyer in pink and purple Comic Sans, but I don't think MS really cares because that market is miniscule compared to Big Business.
> I hate Microsoft Word the way Winston Smith hated Big Brother.
At the end of that novel, <SPOILER> Winston loved Big Brother. </SPOILER> Because he probably realized that no other program but Big Biz MS Word would fit the use cases that it was designed for. LibreOffice? Call me again when it gets the Review function right. Your average college professor isn't going to learn how to use a version control system to suggest changes to his student's thesis-in-progress.