all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: Elisp addiction not as bad in light of Linux forkoholism
Date: Sun, 30 Nov 2014 17:14:42 +0100	[thread overview]
Message-ID: <8761dwis25.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <873891sgaw.fsf@debian.uxu>


On 2014-11-30, at 01:06, Emanuel Berg wrote:

> It is simple: Don't fork - program.

Wow, it's rant time!

So you're in for a treat: I have a spare minute, and let me share a
story with you.  (I guess I read it in some interview, I don't remember
now.)

When DEK coded TeX (and published the cource code), he thought that many
people will actually customize TeX (=the engine) to their needs.  It
turned out that (apparently) the macro programming was more powerful
than he expected: almost nobody did that, people did wonderful things at
the macro level, without ever touching the source code (apart from
increasing the memory constraints, which required recompliation back
then).  This includes not only LaTeX and its styles (later: classes and
packages), but also a BASIC and Lisp interpreters, a few numerical
engines, a regex engine (recently), an XML parser and much more.  (This
is, in fact, an oversimplification; some of these things require e-TeX,
which is a relatively small extension to the engine.)

The real hacking on the underlying engine did happen, of course, but not
that often.  Most notably, we have e-TeX, pdfTeX (which is great),
pdfeTeX (which combines both of them); then we have XeTeX (originally
only on Mac, now also Win and Linux), Omega and Aleph, and - most
recently - LuaTeX (which is the most serious modification, and a very
well designed one AFAIK).  (There were admittedly smaller extensions,
like encTeX, but they could be technically just patches, not "forks".)
Not really that many "forks", for a program more than 30 years old.
Especially that eTeX and pdf(e)TeX are not considered forks now, rather
legal successors (hardly anyone uses the original tex engine nowadays),
and LuaTeX gains more and more traction; some (me included) hope that it
will mostly replace the more conservative versions some day.  (LuaTeX is
AFAIK the only one which took the idea of giving TeX really new things
seriously.)

(Well, there was also NTS, but it was really a clone, not a fork, and it
is almost "evaporated" in Orwellian sense (even the sources are nowhere
on the 'net!) - go figure.)

I guess it is a bit similar as in the Emacs world.  If you make a
program flexible enough, people won't fork it too much - they just won't
need it.  (The existing forks solved some /real problems/: 8-bit-ness
with Omega, complicated dvi->ps->pdf route with pdfTeX, limited
registers and other constraints with eTeX, impossibility of RtL
typesetting with Omega and XeTeX, lack of access to system fonts with
XeTeX, problems with advanced programming and other things with LuaTeX.)

Just my 2 cents.

(And re: Debian vs Ubuntu, I never used Debian, but Ubuntu is a huge
disappointment: it has been less and less usable recently (especially
compared to, say, five or seven years ago), and it will be kicked out of
my machine when I have a few spare days to do a reinstall.)

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



  parent reply	other threads:[~2014-11-30 16:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30  0:06 Elisp addiction not as bad in light of Linux forkoholism Emanuel Berg
2014-11-30  1:22 ` Filipp Gunbin
     [not found] ` <mailman.14979.1417310548.1147.help-gnu-emacs@gnu.org>
2014-11-30  1:49   ` Emanuel Berg
2014-12-01 12:17     ` Filipp Gunbin
     [not found]     ` <mailman.15048.1417436297.1147.help-gnu-emacs@gnu.org>
2014-12-12  2:07       ` Emanuel Berg
2014-11-30  5:16 ` Pascal J. Bourguignon
2014-11-30  6:05   ` Dan Espen
2014-11-30 14:56     ` Emanuel Berg
2014-11-30 17:04     ` Pascal J. Bourguignon
2014-12-01 17:56       ` Dan Espen
2014-12-01 18:41         ` Rostislav Svoboda
     [not found]         ` <mailman.15078.1417459356.1147.help-gnu-emacs@gnu.org>
2014-12-01 20:13           ` Dan Espen
2014-12-12  2:09           ` Emanuel Berg
2014-11-30 14:51   ` Emanuel Berg
2014-12-12  3:42   ` Emacs and Unix (was: Re: Elisp addiction not as bad in light of Linux forkoholism) Emanuel Berg
2014-11-30 16:14 ` Marcin Borkowski [this message]
     [not found] ` <mailman.15000.1417364114.1147.help-gnu-emacs@gnu.org>
2014-11-30 17:35   ` Elisp addiction not as bad in light of Linux forkoholism Emanuel Berg
2014-11-30 18:36     ` Marcin Borkowski
2014-11-30 19:27       ` H. Dieter Wilhelm
     [not found]       ` <mailman.15012.1417375681.1147.help-gnu-emacs@gnu.org>
2014-11-30 19:43         ` Emanuel Berg
2014-11-30 20:18           ` Marcin Borkowski
     [not found]           ` <mailman.15021.1417378703.1147.help-gnu-emacs@gnu.org>
2014-11-30 22:21             ` Emanuel Berg
2014-11-30 22:30           ` H. Dieter Wilhelm
     [not found]           ` <mailman.15028.1417386648.1147.help-gnu-emacs@gnu.org>
2014-12-12  1:55             ` Emanuel Berg
     [not found]     ` <mailman.15006.1417372637.1147.help-gnu-emacs@gnu.org>
2014-11-30 19:41       ` Emanuel Berg
2014-11-30 18:16 ` Nikolay Kudryavtsev
     [not found] ` <mailman.15002.1417371387.1147.help-gnu-emacs@gnu.org>
2014-11-30 18:32   ` Emanuel Berg
2014-12-02 14:50 ` Raffaele Ricciardi
2014-12-02 15:07   ` Eli Zaretskii
     [not found]   ` <mailman.15150.1417532856.1147.help-gnu-emacs@gnu.org>
2014-12-02 16:01     ` Loris Bennett
2014-12-02 17:00       ` Eli Zaretskii
2014-12-03  1:44       ` Stefan Monnier
     [not found]       ` <mailman.15187.1417571105.1147.help-gnu-emacs@gnu.org>
2014-12-12  2:38         ` Emanuel Berg
2014-12-12  2:17   ` Emanuel Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761dwis25.fsf@wmi.amu.edu.pl \
    --to=mbork@wmi.amu.edu.pl \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.