Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Jun 2010 23:22:14 +0200
From:      Polytropon <freebsd@edvax.de>
To:        Roland Smith <rsmith@xs4all.nl>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: office apps
Message-ID:  <20100606232214.4146453e.freebsd@edvax.de>
In-Reply-To: <20100606210311.GA20105@slackbox.erewhon.net>
References:  <20100606203416.GF46089@libertas.local.camdensoftware.com> <20100606223826.62a42f7a.freebsd@edvax.de> <20100606210311.GA20105@slackbox.erewhon.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Jun 2010 23:03:11 +0200, Roland Smith <rsmith@xs4all.nl> wrote:
> Don't forget LaTeX! Especially since it is quite easy for scripting languages
> to generate LaTeX code (automation).

Oh, but *I* didn't forget LaTeX. The OP requested a word processor, 
not a typesetting system (which is the next evolutionary step). :-)

But you are right: LaTeX is excellent because it does all the things
right that word processors do get right after you invested several
hours configuring them, or don't get it right at all.

In this relation, LyX should also be mentioned, a kind of "WYSIWYG"
interface to LaTeX (inaccurately spoken).



> > > If it could also be used without X11 when
> > > charting isn't needed, that would make my day.
> > 
> > CVS for data, C or awk for processing, gnuplot for plotting. :-)
> 
> For real data munching, programming languages do a much better job indeed.

Especially if efficiency is a topic ("number crunching"), nothing
beats native binary code.



> May
> I also suggest Perl, Lua and Python al alternatives to C and awk?

Especially Perl is worth mentioning.



> And 'make'
> to tie everything together. 

Totally agreed; I also (ab)use it for controlling tasks (like making
web pages out of statistical data).



> Unless your machine is severely underpowered or
> your datasets are _huge_, scripting languages tend to be fast enough for data
> processing, IMHO.

And of course a bit more comfortable to use.



> The general weakness of office suites is _automation_, something that programs
> following the UNIX philosophy excel at. (pardon the pun). Quoting Doug McIlroy:
> 
>     This is the Unix philosophy: Write programs that do one thing and do it
>     well. Write programs to work together. Write programs to handle text streams,
>     because that is a universal interface.

A nice summary. And true.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100606232214.4146453e.freebsd>