4 ms·
This is an excellent point. For me, the word change on your first line is what really demonstrates it: many people conflate TeX and LaTeX, because LaTeX is Te
by JadeNB 16y ago
This is an excellent point. For me, the word change on your first line is what really demonstrates it: many people conflate TeX and LaTeX, because LaTeX is TeX; or, to put it less controversially, LaTeX is written in TeX (rather than other (wonderful) extensions, like PDFTeX, XeTeX, or LuaTeX, all of which require source-level changes). LaTeX 3 (http://www.latex-project.org/latex3.html http://www.latex-project.org/latex3.html) takes this even further—and all this drives home the point (which I hope I may safely assert here as fact) that it's often much better to start with a simple programming language and customise it to your need, than to have a high-level programming language painstakingly customised and tuned for an application that turns out to be two millimetres to the left of the one that you actually want.
- crazydiamond 16y ago>it's often much better to start with a simple programming language and customise it to your need, than to have a high-level programming language painstakingly customised and tuned for an application that turns out to be two millimetres to the left of the one that you actually want. I am interested to know if you had other examples in mind when you said this. Disclaimer: not trying to start a discussion on languages, or lang war.
- JadeNB 16y ago> I am interested to know if you had other examples in mind when you said this. Disclaimer: not trying to start a discussion on languages, or lang war. I'm not sure why you'd want to disclaim trying to start a discussion on languages; it seems like a good thing. The sentence I wrote was originally intended just to describe TeX, but it seemed to me in retrospect that it applied almost as well to Lisp. Although the design philosophies of the two languages are completely different, both are intended to be the foundations for lots of little languages; Knuth has said that he was always surprised that people were happy to settle so quickly on TeX and LaTeX, rather than creating and selecting among many more specialised dialects. (Of course, a quick glance at CTAN shows that it is folly to think that everyone who uses TeX or LaTeX does the same thing with it!) I posted some more examples of highly customisable little languages at http://news.ycombinator.com/item?id=1535807 http://news.ycombinator.com/item?id=1535807, but I should mention that I haven't used them.
- jonsen 16y ago"late x": unknowns late in the process ;-)
- HilbertSpace 16y agoThat's why I use TeX. I understand it fairly well, have a lot of macros that work well, and can write more macros easily. So I have own macros for table of contents, cross references, numbering figures, tables, chapters, sections, theorems, etc., bibliographic entries, verbatim, putting text from TeX on figures, putting a frame around foils, lists, etc. With LaTeX, (1) I would have to learn more and (2) to write macros, I might have to understand and then fight what LaTeX assumes. Also the LaTeX documentation is much larger than 'The TeXBook'! So, I just stay with TeX. Also for me a big, HUGE, point is that input to TeX (or LaTeX) is just a simple 'flat ASCII' text file, and for those I use my favorite, programmable text editor, the same one I use for writing software, e-mail, and much more. E.g., when I need to do some special thing to a TeX file, I can write an editor macro to do it. Net, in my general purpose, long lasting collections, I have about 150 macros for TeX, about 150 for my programmable editor, and about 100 for command line scripts. So, that's 400 names to remember? No, from my editor, I can quickly see all the names of all the macros and, of course, for each macro its source. Searching for macros? My editor is great at searching! Lacking anything else, I can quickly pull all the macros of one collection into one temporary file and just search that. I have no difficulty finding macros! Works well. Not to be missed, I run TeX from a scripting language which is 'smart' enough to do the converstion to PDF, etc. So, I minimize clicking. It's easy: I just have a little text window, and to see the results of a change in my TeX input I just hit the retrieve key in that window and then Enter. It's FAST. Broadly I like 'windows', lots of windows, even for just one piece of work. So, for TeX I will have at least three, one for each of my text editor, the TeX DVI preview output, and the command line scripts. For my current software project, putting a Web site in front of some of my other software, I have about 15 windows with a mixture of Web browser windows and my editor windows. To open all those windows at the start of work, I have a simple script. To arrange the windows, I have a simple script. When the windows on the screen get to be a mess, I have a simple script that will arrange them and can be executed with an icon on the UL corner of my screen. Lesson: One 'application' that has just one window and tries to do everything within just that one window is less good than just using the ability of the operating system to display many windows. So, right, "Look, Ma, no IDE!". And no Word, either. End of my contrarian view of graphical user interface!
- eitally 16y ago