Show HN: RinohType – A modern LaTeX in 6500 lines of Python

LaTeX is much nicer to hand edit, and if you're not hand editing you may as well use Word or something.

Probably. I applaud efforts to try to rethink typesetting, and this is clearly a substantial accomplishment. Tex is, however, an outstanding design, both in a number of of its aspects and as an overall design, and a lot of later effort has gone into remedying its limitations.

> TeX is not transparent. It is a huge, complex system ... With hundreds of megabytes and seemingly millions of files for a typical TeX installation, I have no idea what is going on when TeX processes a document.

Knuth's contribution is, in fact, quite small in terms of Mb. This covers just the Computer Modern Roman fonts and the eufrak maths fonts, and Plain Tex. Most of a system such as a full Texlive install is made up of fonts. It covers a huge number of specialist journal styles, and support for the needs of specialist fields (linguistic glosses, setting code, chemical notations, Feynman diagrams, etc.). The complexity is that of a library, and kpathsea is its index system.

I have the idea that maybe you think a package whose value you don't see is fluff: there is fluff in Texlive, but probably much less than you think.

> The arcane TeX macro language is not accessible to a broad audience. I believe this is why most LaTeX-generated documents you come across have exactly the same (retro) look; very few people are capable of creating new document styles.

There is a point here, but I think the reason is that most people don't want to fuss about with style. CSS makes it easy to experiment with page styles, and still most web pages either follow a standard formula or look very ugly. Understanding markup conventions is not usually going to be the biggest obstacle to achieving good design.

> TeX is not very modern

There is not a real problem outlined here: you could equally say that the basic layout engine has proven itself by being capable of accommodating all these later technologies. The Office 2007 team even rewrote its formula layout engine so that it would conform to that described in the Tex book, and employed Knuth as a consultant.

I'd put it this way: Knuth's code combines a very deep insight into the nature of the requirements of computer typesetting with outstanding implementation skills. The basic design has not really been surpassed.

> TeX’s warnings/errors are often very cryptic. It can sometimes take a long time to figure out what’s wrong.

Yes, very much so. This is probably the best reason to consider alternative document description languages. But note that Tex is very successful at allowing "code" invocation to be mixed with text - I'd like to see rivals that challenge Tex on this point.

> But why do I even need to mess around with all these extension packages when all I’m doing is writing a simple article? Doesn’t this mean that LaTeX should include at least some of the most commonly used packages by default?

The Latex3 team concede this. Context, a rival Tex-based system, does not have this problem.

> This might largely be a solved problem by now, but I remember often running into input and font encoding issues with LaTeX in the past.

Use Xetex or Luatex, and standardise everything on Unicode; these problems go away.

> There is no strict separation of content and style.

I'd put it this way: the system offers the possibility of such a separation, but does not enforce it. This is bad if you often have to work with other people's Latex, although in practice, you learn how to deal with it.

Addressing some of the problems raised in http://tex.stackexchange.com/questions/128454/are-there-any-... could be helpful for showing off your design and the advantages of a fresh start.