Re:Editing the C Standard
by olivierestsage on Friday November 13, 2020 @03:33PM
(#25087127)
I understand that the author wants to make a provocative statement/get a reaction, but I have to say I find the general tone of this post, and especially the claim "LaTeX is horseshit", extremely off-putting (not to mention clueless as to both the historic and continued significance of LaTeX). It makes me not even want to bother trying to discern whatever point the author might be attempting to make.
Re:Editing the C Standard
by zzless on Friday November 13, 2020 @04:04PM
(#25087483)
I would also point out that most of his troubles stem from the somewhat amateurish approach to using LaTeX. Overfull boxes can be handled by relaxing the typographic requirements. If one desires the typesetting quality of MS Word and quicker builds, this can be easily arranged by manipulating \emergencystretch and such. LaTeX is not an editor, and the use of a carefully designed style would go a long way to eliminate most of his concerns. But proclaiming 'do not write documents in LaTeX, use Word instead' is just subjective garbage, to use his own terminology. Disclaimer: I do not particularly like LaTeX and prefer plain TeX myself.
Re:Editing the C Standard
by Tyr42 on Friday November 13, 2020 @03:52PM
(#25087339)
To be fair, I've written my math papers in LaTeX, and I agree. Well, perhaps with the modification: "LaTeX errors are complete horseshit". Or perhaps blame the compiler.
Do you remember what gcc errors were like just as clang got popular? They were pretty bad before the c compilers started competing to have nice ones.
Those are wonderful in comparison to the errors in LaTeX.
Fucking extra newline breaking equation* and causing nonsense.
Re:Editing the C Standard
by chrisseaton on Friday November 13, 2020 @04:21PM
(#25087654)
LaTeX is the work of real people with feelings. You can criticise work without resorting to abuse. Also if you resort to abuse it makes me suspicious that you don’t have a strong enough argument without the theatrics.
Re:Editing the C Standard
by wahern on Friday November 13, 2020 @04:44PM
(#25087861)
Not just that, but AFAIU the switch to LaTeX is a relatively recent thing and accomplished by someone whose judgment I value far more than that of the article author.[1] Granted, I've never even heard of the article author before and was surprised the editor baton had been passed.
In general complaining in such terms about a project you've just taken over doesn't seem very professional.[2] We've all been there, done that, etc. LaTeX diagnostics are atrocious. All received large projects are filled with decisions one wouldn't have made oneself, and consequences one would have avoided. But it pays to remember that any senior engineer has presumably left in their wake several large projects that befuddled and frustrated subsequent maintainers, both because of regrettable reasons, yet also for reasons that one would readily defend.
But to suggest Microsoft Word as being a superior option... I can't even begin to fathom such a comparison. I can imagine, however, how insanely frustrated and pissed I would be if I had to take over the task of managing a huge, complex Microsoft Word document. I'm also prepared to admit that there may exist a universe (in which I might be living) where Word is a defensible choice over LaTeX, and that the choice might be more akin to common religious preferences--vi vs emacs, CLI vs GUI, etc--and not something that can be strictly judged in objective terms. Hopefully that admission would give me pause before I let loose such a tirade.
[1] AFAIU, Jens Gustedt was the previous editor, both initiating and executing the switch to LaTeX. But I've never participated in the committee. I may have had a mistaken belief about who was doing the editing over the past several years.
[2] That's a comment on the article, not on the author himself. Professionals do unprofessional things all the time.
Re:Editing the C Standard
by dang on Friday November 13, 2020 @03:55PM
(#25087358)
Please don't editorialize the title (submitted title was "Editing the C standard / “LaTeX is horseshit”"). This breaks the site guidelines: "Please use the original title, unless it is misleading or linkbait; don't editorialize." (https://news.ycombinator.com/newsguidelines.html)
I realize there was a subheading saying that, but the article has other subheadings, and cherry-picking is the essence of editorializing. Titles have by far the biggest influence on discussion, so this is a big deal.
Re:Editing the C Standard
by Dylan16807 on Friday November 13, 2020 @07:15PM
(#25089087)
So what are you supposed to do, if you want to submit a document that is stuck inside a larger document? Any method I can think of would fail the "original source" rule.
Re:Editing the C Standard
by bovermyer on Friday November 13, 2020 @03:37PM
(#25087174)
I use LaTeX because I can define both layout and content in text files. I can store those files in git, and generate a quick PDF from them.
I used to use pandoc (with pandoc-flavored Markdown) for this, but it just couldn't handle layout properly, even with mixed LaTeX and Markdown in the same files.
I'm not overly fond of LaTeX, but it is the only tool that does what I want.
Re:Editing the C Standard
by LEARAX on Friday November 13, 2020 @03:57PM
(#25087402)
It's really unfortunate that LaTeX and friends seem to be the only options for document typesetting with anything vaguely complicated. There are just so many quirks and oddities; many times I feel like error messages might as well be written in another language, and the syntax becomes ugly fast. Personally I haven't had much luck getting into LuaLateX or XeLaTeX, but I'd be interested in hearing if anyone has found those to be worthy alternatives. Having looked into LuaLaTeX a bit, it seems there are a lot of odd quirks there as well.
Re:Editing the C Standard
by wahern on Friday November 13, 2020 @05:09PM
(#25088111)
LaTeX and its TeX cousins are the worst document typesetting options except for all the others.
What's fascinating is that this situation has existed for decades. Alternatives have risen and [mostly] fallen, but LaTeX persists. For that reason an alternative would not only have to be better, but significantly better, for me to question someone's choice of LaTeX.
Re:Editing the C Standard
by Tainnor on Friday November 13, 2020 @09:21PM
(#25089744)
This. It's also hilarious how bad LaTeX actually is at maths despite it being overwhelmingly used for exactly that purpose. Instead of worrying about mathematical semantics, you constantly have to make typesetting decisions. There are workarounds (use your own custom, semantic commands), but still. And yet, everything else seems to be even worse.
Disclaimer: I have been using LaTeX (mostly XeLaTeX) for over a decade for most of my writing, mathematical and non-mathematical, although nowadays I often do so via Markdown+pandoc. Also, at my last company we had to parse mathematical formulas typeset in LaTeX and understand their structure... it was a nightmare.
Re:Editing the C Standard
by mhh__ on Friday November 13, 2020 @03:18PM
(#25086950)
I don't think LaTeX is that bad but...
As a community (programming, engineering, science - whatever) we should probably be louder that the one thing any man or woman with the raw cash can do to help the scientific community is funding LaTeX-2030. The problem is oh-so-difficult but having a modern statically typed (for reflection mainly) well-designed programming language for typesetting could save huge amounts of time for researchers and the like.
That and the real agenda which is to kill word.
The degrees of separation from the HN readers stereotype of a HN reader to a billionaire can't be that high, right?
Re:Editing the C Standard
by markgall on Friday November 13, 2020 @03:28PM
(#25087070)
I don't really believe this. Fund some open access initiatives or something and your money will go a lot further.
The vast majority just don't have a use case where "LaTeX-2030" is going to help, and this wouldn't make much difference to them. I'm a mathematician and I write papers in LaTeX every day. Sure I could benefit from programability occasionally, but it's just not a serious problem. If I need to automatically generate a table or something, I have a Python script output LaTeX, it takes me 30 seconds.
Obviously there are some uses cases where it would make a big difference, but there just aren't very many in the grand scheme. We already have LaTeX3 which lets you do scripting, and lualatex. The fact that basically nobody uses either gives you a sense of how much the general community wants this.
Re:Editing the C Standard
by y7 on Friday November 13, 2020 @04:07PM
(#25087517)
LaTeX indeed mostly works. But, I do think it could be a lot better. For example, today while writing a paper, I ran into a compilation issue that gave me the following error message:
None of these commands (except \end{theorem}) were in my paper, they were all in an included package. I later found out the issue was nowhere near line 350 or inside of the theorem environment. There just doesn't seem to be a good way to debug LaTeX errors. The best method I found was to use some sort of binary search, removing parts of the document to see if the error persists — which is ridiculously time consuming.
I think they meant a hypothetical replacement for LaTeX that would come into existence as a result of that funding and would be ready by 2030, rather than a project that actually exists now.
Is that aimed at the grandparent commenter (mhh__) for an insufficiently clear comment, or the parent commenter (pklausler) for not reading it correctly? I found the original comment perfectly clear but evidently several others didn't, so it really could mean either. I can't help, though, pointing out the irony that your comment is ambiguous. Maybe the problem isn't literacy but just that language is hard.
Re:Editing the C Standard
by jessaustin on Friday November 13, 2020 @07:17PM
(#25089107)
Ordinarily one would say that one who understands {less, more} is {less, more} literate. The base case is Babel: complete mutual incomprehension, like unto that of the beasts. Any who leave this state, in no matter which direction they leave, have read and understood. So, I can't in good conscience answer your question. Language is just exactly what we make of it.
Irony, on the other hand, is a single message for multiple audiences. It requires a degree of mutual incomprehension.
Re:Editing the C Standard
by mhh__ on Friday November 13, 2020 @09:41PM
(#25089830)
I close to giving up on trying to be clever or poetic on HN, I think the implicit no jokes or fun rule means people just switch their brains off and I end up having to explain it (This particular comment not so much, but still)
Re:Editing the C Standard
by 0xffff2 on Friday November 13, 2020 @03:27PM
(#25087059)
I've never heard of "LaTeX-2030", and even adding terms like "typesetting" and "language" to filter out the gloves (and other less SFW results...), I still don't find anything relevant. Whatever it is, I guess they must really need the funding if they can't even make it onto the front page of Google.
Re:Editing the C Standard
by rnhmjoj on Friday November 13, 2020 @03:40PM
(#25087207)
So, what are the LaTeX alternatives that I can use to create high quality documents with source I can check into a CVS, great tooling and documentation?
Re:Editing the C Standard
by kickingvegas on Friday November 13, 2020 @03:31PM
(#25087098)
FWIW, I used but never liked LaTeX and only because I needed a good way to deal with expressing mathematics.
However, using org-mode and exporting to LaTeX is a winning combo for me. With org-mode, I can focus on writing and not typesetting.
Re:Editing the C Standard
by masklinn on Friday November 13, 2020 @03:39PM
(#25087193)
> However, using org-mode and exporting to LaTeX is a winning combo for me.
Yeah there are plenty of relatively easy to use lightweight markup languages which can generate LaTeX[0]. If you don't need the specific properties of LaTeX but want the option of LaTeX-typeset output, use something else and compile to PDF through LaTeX.
[0] because Pandoc generates LaTeX even if the reference implementation doesn't.
Re:Editing the C Standard
by phaemon on Friday November 13, 2020 @03:38PM
(#25087183)
You know, for over a decade I've basically lived in vim & the shell. But I continually hear good things about org-mode and magit. Should I just embrace my destiny turn to the dark side?
Re:Editing the C Standard
by kickingvegas on Friday November 13, 2020 @04:23PM
(#25087680)
Would not frame it as “destiny” or “dark”, but using org-mode has been spectacularly transforming and guiding for how I plan/design software today. Definitely worth trying out https://orgmode.org/features.html
Re:Editing the C Standard
by kickingvegas on Saturday November 14, 2020 @01:21AM
(#25090651)
Okay, here's a typical day with org-mode for me. Start out the day entering a daily journal, listing out all the TODO items and scheduling them so I can see them in org-agenda. A subset of those TODOs are meetings, of which I'll use the folding outline editor to write an agenda and notes. Given that I work remotely now near 100% of the time, I typically share my screen to go over the agenda. Frequently, I'll need to diagram something to share with the team. For that I use org-babel to write plantuml or graphviz and render the output (like a sequence or class diagram or flow chart) and use that to drive design discussion with the team. Note that all of this is still within GUI emacs in single buffer (text and images). At my work we use Confluence and Jira, so I use org-export to publish the above work to Jira markup (tables, headings, lists, typeface styles). Other TODO items are the tasks I do during the day; there I use org-mode to capture my notes/thoughts. Most times, I'll use org tables to help organize tabular data (which happens a lot) and org-babel to run both python and bash commands. In addition I'll use source blocks to capture code snippets (typically Swift nowawdays) and random commands. I'll also store links that I run across through the course of day. Note again, I'm still working out of that same buffer. With emacs-client, I remote from my iPad into that same buffer and edit away. End of the day, I commit my org-mode file into my notes repo using magit. Occasionally, I'll use org-mode to write a presentation using reveal.js or typeset documentatation to push through LaTeX. Nearly all my documentation starts out as an org file. YMMV, but org-mode has completely transformed how I work now.
"On most measures, expert LaTeX users performed even worse than novice Word users."
However, it is worth noting that anyone who has ever dealt with a Word document that is a collation from other people usually winds up with similar to hassles to what the writer finds in the article.
Re:Editing the C Standard
by markgall on Friday November 13, 2020 @03:56PM
(#25087381)
This paper has been criticized in many places, because the way it's set up of course Word will win. People had to do things like very specific figure placement that is difficult in LaTeX.
But in reality, most people just accept how LaTeX handles the figure placement by default (which is usually quite good), and doesn't waste time fighting it. So it's not really a real-life comparison of the two.
If the challenge had been "Write a document formatted according to the norms of your field", which is what people are actually doing most of the time, LaTeX would win easily. For scientific papers the journal is going to redo all the formatting anyway (using their own custom LaTeX set-ups), so there's no reason to waste time on this.
Re:Editing the C Standard
by zzless on Friday November 13, 2020 @04:13PM
(#25087560)
Indeed, one look at the comments would unveil a whole lot of shortcomings to their methodology. One of which was an entirely opaque way in which they defined 'errors in typesetting'.
Re:Editing the C Standard
by jcranmer on Friday November 13, 2020 @04:21PM
(#25087655)
> But in reality, most people just accept how LaTeX handles the figure placement by default (which is usually quite good), and doesn't waste time fighting it.
In my experience, LaTeX's default figure placement is actually quite bad, and you have to spend some time trying to paste it in different places to get it to place the figure in the place you want it.
Re:Editing the C Standard
by hpoe on Friday November 13, 2020 @03:58PM
(#25087406)
An interesting article. I'll offer my counterpoint is the fungiblity of a LaTeX document. It is at the end of the day an opens source text based standard. That means I can easily put it in git, I can easily modify it in my favorite text editor (doom emacs) that I've already configured for my personal workflow. It means the document is light, and it means that I don't have to worry about everyone I send it to having the right software.
Re:Editing the C Standard
by mhh__ on Friday November 13, 2020 @03:20PM
(#25086974)
It's also decades old and positively crap if you try and treat it like you would a modern programming language. It's way too difficult a problem to do on a whim but quite a lot of time in academia is just thrown down the pit of LaTeX (be that due to incompetence or the design being older than various principles e.g. DRY)
LaTeX is certainly the best LaTeX, but it doesn't really have that many competitors.
Re:Editing the C Standard
by brundolf on Friday November 13, 2020 @04:26PM
(#25087710)
What's the reason it doesn't have many competitors? Is it intrinsically too hard of a problem, or is it a matter of network effects (extensions, existing knowledge, existing bodies of work, etc)? Or is there just a lack of motivation?
Re:Editing the C Standard
by jcranmer on Friday November 13, 2020 @04:53PM
(#25087966)
There's kind of two steps to the process: the composition of text, and then the fine-tuning to make the composed text look neat. These two steps are not so easily divorced from one another, though, especially when you're dealing with multiple rounds of edits, so it doesn't work too well to force these to be separate tools to deal with the task.
There's a lot of competitors to the first step, in the vein of having multiple tools that are plain-text files but convert to rich-text output. However, most of these tools lack good, or even any, support for the fine-tuning capabilities. Where there is competition in the fine-tuning space, the relevant tools are largely based on WYSIWYG editors--which makes sense when you consider that it's easier to fine-tune properties when you get immediate visual feedback on what the fine-tuning you're doing does to the result. But these editors don't provide an easy way to integrate in the workflows of the other tools, since the underlying formats don't really support the fine-tuning capabilities.
Re:Editing the C Standard
by brundolf on Friday November 13, 2020 @04:44PM
(#25087866)
It's something I'm (probably foolishly) tempted to take a swing at. I have a lot of experience with doing layout in HTML/CSS (of which printable typesetting feels like a subset, superficially at least), and I've been getting into writing parsers/doing language design recently. The only problem is I don't know a ton about LaTeX or how people use it other than "it lets you very precisely format documents via special markup, including things like mathematical formulas and diagrams (?), and it's used by lots of academics".
Re:Editing the C Standard
by zzless on Friday November 13, 2020 @05:43PM
(#25088450)
I respect your courage but I have to disagree with your assessment of CSS vs real typography. Layout capabilities of CSS are orders of magnitude less extensive compared to those of TeX. For example it is nearly impossible to say, put a box 2/3 of the width of a container of unknown width. Just the simple task of centering an element has pages dedicated to it and to my knowledge, only CSS3 has a reasonably workable solution. As far as LaTeX's abilities as a programming language go, I have an interpreter for a reasonable subset of C written in TeX (it was an academic exercise but this is just to show what is possible). So it is much more than a mere markup language.
Re:Editing the C Standard
by brundolf on Saturday November 14, 2020 @11:26AM
(#25093250)
> For example it is nearly impossible to say, put a box 2/3 of the width of a container of unknown width. Just the simple task of centering an element has pages dedicated to it and to my knowledge, only CSS3 has a reasonably workable solution.
It's been a few years since you used CSS :) Both of these things are trivial to do now
But to be clear: while I think my CSS experience would give me a grasp of what needs to be expressed and some ideas for how to express it, there is a whole other layer of actually applying that, and reconciling it with the content, which would be a challenge (and is done for you by the browser in CSS' case)
> As far as LaTeX's abilities as a programming language go, I have an interpreter for a reasonable subset of C written in TeX (it was an academic exercise but this is just to show what is possible). So it is much more than a mere markup language.
I believe you, but I also question whether that level of power is actually being used by people making documents with it, or whether it just adds complexity. I genuinely don't know. But those are the kinds of places one might find improvements to be made.
Re:Editing the C Standard
by zzless on Saturday November 14, 2020 @09:04AM
(#25092340)
I would like to second this great advice. A somewhat shorter piece of reading is 'Mathematical typography' by Knuth (published in the Bulletin of the AMS but I believe is freely available online). This article outlines the (enormous) scope of the problem (even before multilanguage typography is considered, or any graphics for that matter).
Re:Editing the C Standard
by CJefferson on Friday November 13, 2020 @03:30PM
(#25087094)
It's full of defects, they'll just never be fixed. Most languges would define the error messages of LaTeX as defects, and once you start including packages, many don't work together.
I never realised how awful LaTeX was until I started working with a co-author who is blind, if you just "write LaTeX" you end up with equations, algorithms and tables constantly half-off the page.
Re:Editing the C Standard
by johnday on Friday November 13, 2020 @03:36PM
(#25087157)
LaTeX does report this as a problem, of course - the refrain of "overfull hbox" is near universal (and ignoring the warning is just as universal).
Where it fails is in reporting the problem in a meaningful way. This is, of course, very difficult to accomplish, since there is no nice mapping from line-of-TeX to visual error. What's more, any tool which could provide such an error would be so constrained as to be useless for typesetting.
Re:Editing the C Standard
by Tomte on Friday November 13, 2020 @03:17PM
(#25086944)
That's obviously wrong. You're probably thinking of TeX which is bug-free, due to a combination of (a) Donald Knuth being a genius, (b) extreme scrutiny of the code base (in part because of the reward cheques) and (c) Knuth having defined it as bug-free years ago.
Re:Editing the C Standard
by jcranmer on Friday November 13, 2020 @04:12PM
(#25087554)
> (c) Knuth having defined it as bug-free years ago.
IIRC, TeX only becomes defined bug-free on Knuth's death. However, it is feature-complete, in the sense that there are no more features to be added, even if such functionality is desperately needed. (Most notably, TeX does have issues with i18n and especially right-to-left text support)
Do you remember what gcc errors were like just as clang got popular? They were pretty bad before the c compilers started competing to have nice ones.
Those are wonderful in comparison to the errors in LaTeX.
Fucking extra newline breaking equation* and causing nonsense.
In general complaining in such terms about a project you've just taken over doesn't seem very professional.[2] We've all been there, done that, etc. LaTeX diagnostics are atrocious. All received large projects are filled with decisions one wouldn't have made oneself, and consequences one would have avoided. But it pays to remember that any senior engineer has presumably left in their wake several large projects that befuddled and frustrated subsequent maintainers, both because of regrettable reasons, yet also for reasons that one would readily defend.
But to suggest Microsoft Word as being a superior option... I can't even begin to fathom such a comparison. I can imagine, however, how insanely frustrated and pissed I would be if I had to take over the task of managing a huge, complex Microsoft Word document. I'm also prepared to admit that there may exist a universe (in which I might be living) where Word is a defensible choice over LaTeX, and that the choice might be more akin to common religious preferences--vi vs emacs, CLI vs GUI, etc--and not something that can be strictly judged in objective terms. Hopefully that admission would give me pause before I let loose such a tirade.
[1] AFAIU, Jens Gustedt was the previous editor, both initiating and executing the switch to LaTeX. But I've never participated in the committee. I may have had a mistaken belief about who was doing the editing over the past several years.
[2] That's a comment on the article, not on the author himself. Professionals do unprofessional things all the time.
I realize there was a subheading saying that, but the article has other subheadings, and cherry-picking is the essence of editorializing. Titles have by far the biggest influence on discussion, so this is a big deal.
I used to use pandoc (with pandoc-flavored Markdown) for this, but it just couldn't handle layout properly, even with mixed LaTeX and Markdown in the same files.
I'm not overly fond of LaTeX, but it is the only tool that does what I want.
What's fascinating is that this situation has existed for decades. Alternatives have risen and [mostly] fallen, but LaTeX persists. For that reason an alternative would not only have to be better, but significantly better, for me to question someone's choice of LaTeX.
Disclaimer: I have been using LaTeX (mostly XeLaTeX) for over a decade for most of my writing, mathematical and non-mathematical, although nowadays I often do so via Markdown+pandoc. Also, at my last company we had to parse mathematical formulas typeset in LaTeX and understand their structure... it was a nightmare.
As a community (programming, engineering, science - whatever) we should probably be louder that the one thing any man or woman with the raw cash can do to help the scientific community is funding LaTeX-2030. The problem is oh-so-difficult but having a modern statically typed (for reflection mainly) well-designed programming language for typesetting could save huge amounts of time for researchers and the like.
That and the real agenda which is to kill word.
The degrees of separation from the HN readers stereotype of a HN reader to a billionaire can't be that high, right?
The vast majority just don't have a use case where "LaTeX-2030" is going to help, and this wouldn't make much difference to them. I'm a mathematician and I write papers in LaTeX every day. Sure I could benefit from programability occasionally, but it's just not a serious problem. If I need to automatically generate a table or something, I have a Python script output LaTeX, it takes me 30 seconds.
Obviously there are some uses cases where it would make a big difference, but there just aren't very many in the grand scheme. We already have LaTeX3 which lets you do scripting, and lualatex. The fact that basically nobody uses either gives you a sense of how much the general community wants this.
https://tex.stackexchange.com/questions/309010/teach-me-to-d...
Irony, on the other hand, is a single message for multiple audiences. It requires a degree of mutual incomprehension.
https://news.ycombinator.com/item?id=22865357
https://news.ycombinator.com/item?id=22865357&p=2
https://news.ycombinator.com/item?id=22865357&p=3
https://news.ycombinator.com/item?id=22865357&p=4
For me great tooling means Word/Framemaker like, with ability to generate whatever document format I feel like.
Yeah there are plenty of relatively easy to use lightweight markup languages which can generate LaTeX[0]. If you don't need the specific properties of LaTeX but want the option of LaTeX-typeset output, use something else and compile to PDF through LaTeX.
[0] because Pandoc generates LaTeX even if the reference implementation doesn't.
https://journals.plos.org/plosone/article?id=10.1371/journal...
Big quote from the abstract :
"On most measures, expert LaTeX users performed even worse than novice Word users."
However, it is worth noting that anyone who has ever dealt with a Word document that is a collation from other people usually winds up with similar to hassles to what the writer finds in the article.
But in reality, most people just accept how LaTeX handles the figure placement by default (which is usually quite good), and doesn't waste time fighting it. So it's not really a real-life comparison of the two.
If the challenge had been "Write a document formatted according to the norms of your field", which is what people are actually doing most of the time, LaTeX would win easily. For scientific papers the journal is going to redo all the formatting anyway (using their own custom LaTeX set-ups), so there's no reason to waste time on this.
In my experience, LaTeX's default figure placement is actually quite bad, and you have to spend some time trying to paste it in different places to get it to place the figure in the place you want it.
LaTeX is certainly the best LaTeX, but it doesn't really have that many competitors.
There's a lot of competitors to the first step, in the vein of having multiple tools that are plain-text files but convert to rich-text output. However, most of these tools lack good, or even any, support for the fine-tuning capabilities. Where there is competition in the fine-tuning space, the relevant tools are largely based on WYSIWYG editors--which makes sense when you consider that it's easier to fine-tune properties when you get immediate visual feedback on what the fine-tuning you're doing does to the result. But these editors don't provide an easy way to integrate in the workflows of the other tools, since the underlying formats don't really support the fine-tuning capabilities.
It's been a few years since you used CSS :) Both of these things are trivial to do now
But to be clear: while I think my CSS experience would give me a grasp of what needs to be expressed and some ideas for how to express it, there is a whole other layer of actually applying that, and reconciling it with the content, which would be a challenge (and is done for you by the browser in CSS' case)
> As far as LaTeX's abilities as a programming language go, I have an interpreter for a reasonable subset of C written in TeX (it was an academic exercise but this is just to show what is possible). So it is much more than a mere markup language.
I believe you, but I also question whether that level of power is actually being used by people making documents with it, or whether it just adds complexity. I genuinely don't know. But those are the kinds of places one might find improvements to be made.
I would love to work on this, but definitely can't commit the time.
I never realised how awful LaTeX was until I started working with a co-author who is blind, if you just "write LaTeX" you end up with equations, algorithms and tables constantly half-off the page.
Where it fails is in reporting the problem in a meaningful way. This is, of course, very difficult to accomplish, since there is no nice mapping from line-of-TeX to visual error. What's more, any tool which could provide such an error would be so constrained as to be useless for typesetting.
IIRC, TeX only becomes defined bug-free on Knuth's death. However, it is feature-complete, in the sense that there are no more features to be added, even if such functionality is desperately needed. (Most notably, TeX does have issues with i18n and especially right-to-left text support)