Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Ars Technia: Word is Dead, Long Live Wikis!

twitter (104583) writes | about 5 years ago

Data Storage 1

twitter writes "A Word fan at Ars Technia has declares death of Word and the rise of Wikis. He completely missed the point of Word Perfect, the OOXML ISO scandal and many other things but there's one thing he did not miss, the typical document flow at most companies sucks life in a way that Wikis fix perfectly.

People keep doing [passing poorly revisioned Word docs in email and storing them in random network locations], but it is an astoundingly awful way to work.

I chose MediaWiki, the open-source software that powers Wikipedia. It was relatively easy to install on a virtual Linux server. ... The real win, however, was that everyone started using it. One day you wake up and everything is on a wiki somewhere. How did that happen? It happens in much the same way as typewriters suddenly disappearedbecause a better alternative arrived. Wordand I know I'll be attacked for saying thisis the new typewriter.

Welcome to the obvious. Print is dead, replaced by easy to use, concurrently editable, well revisioned and easily searched electronic document systems that cost next to nothing to set up. The read write web Lee Berners first imagined is here."
Link to Original Source

cancel ×

1 comment

Sorry! There are no comments related to the filter you selected.

Great for research groups (1)

Kanel (1105463) | about 5 years ago | (#28926009)

Wikis have shown themselves as a slick way to update homepages of say, a research group at a university. With the old homepages, if you wanted to publish a link to the latest paper you had produced, you had to send a mail to some designated webpage-maintainer, typically a student, who eventually fired up his editor then edited and uploaded the relevant page after testing it locally. If something was wrong with the page, you went bitching to him. This student would eventually finish his thesis, leave, and the page went static.

With a wiki, typically everyone in the group has access, everyone can add their own papers, there's no need for FTP to edit or upload photos, no need to know HTML coding. Things get done and they get done quickly. Other groups maintain internal wikis documenting the complicated and often ill-documented lab procedures. You don't set apart a day to produce a memo on the procedure that is then circulated to everyone and has to be re-circulated to new students. Instead you write a few snippets while you'r waiting at the lab-bench, others add in details and the text is always up-to-date, no old copies being circulated around.
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>