It's mostly just subjective nowadays, just like your whole 'argument'.
I think it looks great on high res displays, which should cover a huge chunk of all consumer displays used today.
[1] https://gs.statcounter.com/screen-resolution-stats
[2] https://gs.statcounter.com/screen-resolution-stats/desktop/w...
(This is with the Dark Reader extension in Dynamic mode with these settings: https://0x0.st/-M8g.png)
To excel at math requires focus. When I see Computer Modern I see an author who didn't get distracted choosing a better font. Not just undergraduates.
We need to accept that Knuth was an amateur type designer who was genuinely preoccupied with fonts (“I can’t go to a restaurant and order food because I keep looking at the fonts on the menu.” — Donald Knuth https://twitter.com/TeXtip/status/1389329788628783104). He could have delegated the design of the first font for his TeX system to a professional type designer. He didn't.
Knuth started work on TeX's fonts about the same time that he began work on TeX and Metafont (1977-78). CM was largely completed by about 1984-86. He was a computer science professor. I'm not aware of any funding he procured to develop TeX. You're saying he had the financial resources to hire a professional type designer for fonts for an academic publishing system of unknown future?
Sure, bootstrapping the TeX project would have been a bit more difficult if a font designer had been required from the start; on the other hand, maybe Metafont would have been a more successful font design system if type designers had been (more?) involved from the outset.
"Zapf designed and drew the Euler alphabets in 1980–81 and provided critique and advice of digital proofs in 1983 and later. The typeface family is copyright by American Mathematical Society, 1983. Euler Metafont development was done by Stanford computer science and/or digital typography students; first Scott Kim, then Carol Twombly and Daniel Mills, and finally David Siegel, all assisted by John Hobby. Siegel finished the Metafont Euler digitization project as his M.S. thesis in 1985."
It's worth noting, more generally, that Knuth himself has described a realization that he gets better results from delegating tasks than from "going it alone":
"Some of you may recall that I wrote the entire program for TEX78 and TEX82 all by myself, and you may be wondering whether I’ve done the same for iTeX. Don’t worry: This time around I’m having the job done by people who know what they’re doing. After many years I’ve finally come to realize that my main strength lies in an ability to delegate work and to lead large projects, rather than to go it alone. Programming has never really been my forté for example, I’ve had to remove 1289 bugs from TEX, and 571 from METAFONT."
More concretely: the design of Computer Modern is based on the typeface used for the first edition (10-point Monotype Modern 8A, etc). It's not identical, but you can compare say, the first (1973, Monotype hot metal) and second (1998, using CM/Metafont) editions of Volume 3; it's substantially the same typeface; at least most people's criticisms of Computer Modern would also apply to the font he found so beautiful and which he was trying to reproduce. (Except the "spindly" or "too light" complaint which is not a problem with "true" CM but only with the TrueType/OpenType version used today by nearly everyone except Knuth: see https://tex.stackexchange.com/a/361722/48 and the comment below it, and http://mirrors.ctan.org/fonts/mlmodern/doc/mlmodern.pdf.) In fact, he says he was excited when Addison-Wesley approached him to write a textbook (in the early 1960s) because he loved their typesetting so much.
His goal at first was simply to reproduce the same font digitally (TeX was created only because of the necessity of a system for using those new digital fonts). He approached Xerox (PARC, I think) to use their high-resolution equipment and obtain a digital scan of the Monotype font. If they had agreed unconditionally, that would have been the end of it, and METAFONT wouldn't have existed. They insisted that any font created digitally using their resources would belong to Xerox, which Knuth thought fair but unacceptable to him, so he set out to reproduce the font with the resources available to him. While staring at blown-up images of the letters projected on his wall at home via a TV camera, he had the realization that the shapes were not entirely arbitrary and therefore perhaps he ought to describe the shapes in terms of curves rather than simply capturing the shapes as numbers, and his syntax (and implementation) for describing these shapes turned into METAFONT. His shapes (glyphs) for CM did diverge from Monotype Modern a bit, with all the feedback he got from people like Hermann Zapf and Matthew Carter and Richard Southall and Chuck Bigelow & Kris Holmes and Neenie Billawala (one of the Stanford students)—these are the people credited in the preface to Volume E (Computer Modern Typefaces)—but it's not as if he sat down to design a typeface ab initio in a system that he had already built or was planning to build. METAFONT is simply the collection of tricks/code he came up with for the problem of creating a computer version of Monotype Modern (thus the name, "Computer Modern").
Much of this story is narrated in his Kyoto Prize lecture of 1996 (https://web.archive.org/web/20201111041445/https://www.kyoto...), reprinted as the first chapter of his collected volume Digital Typography.
The last paragraph you quoted is from a joke/satire/parody (https://tug.org/TUGboat/tb31-2/tb98knut.pdf / https://www.youtube.com/watch?v=eKaI78K_rgA) and represents the opposite of his views (https://yurichev.com/mirrors/knuth1989.pdf):
> Thus, I came to the conclusion that the designer of a new system must not only be the implementer and the first large-scale user; the designer should also write the first user manual. The separation of any of these four components would have hurt TeX significantly. If I had not participated fully in all these activities, literally hundreds of improvements would never have been made, because I would never have thought of them or perceived why they were important.
At the risk of stating the obvious, iTeX is not a real successor of TeX, it's a deliberately-vaporware joke.
I do agree though it has been abused a lot as a status symbol. Back at MIT, having a resume in CM spoke "I come from a science/engineering background" right off the bat, while having a resume in a Microsoft font spoke "I go to the business school".
If you move away from CM, great, there are lots of better web-friendly fonts, but don't go to TNR for f*ck's sake. TNR is awful. Unfortunately some publications have gone down this hole.
I like Crimson Pro of late. It looks VERY pleasing on mobile LCD/LED and e-Ink screens, has the effect of making your device feel like a quality printed book, and has a full selection of weights.
The same can be said about P.D.F. files.
I recently found out why so often when copying from them, spaces are either inserted doubly, or removed: the reason is that the format has no understanding of spaces, only of distance between characters and is completely about præsentation, lacking semantics in any way.
When copying, the reader simply applies a heuristic of what distance between characters constitutes a space, and is often wrong.
I think there's just a bunch of history here--print is the use case that you really want PDF to get correct, and so you take existing print pipelines which discard semantics and add PDF as a new backend. This is the easy/lazy way to get PDF working, and there are also tons of PDF pipelines are just stapled onto the end of a print pipeline as if PDF were another type of printer.
You'll see a night and day difference between one of those pipelines and something more suited to processing a document with semantics, like FrameMaker. FrameMaker seems to be a bit more niche now that print documentation is less mainstream.
I can understand why the PDF ecosystem is a bit frustrating, but I still prefer it when I'm reading academic papers explaining some algorithm or mathematical concept.
When the alternative is that they don't offer a non-proprietary export format at all, I'll take it. Even a poor PDF output is better for data portability than having your data forever trapped in a proprietary platform that can disappear or get discontinued at any time without a migration path.
OCR applications are able to make PDFs from scanned images accessible and searchable (and with the right spaces) precisely because they embed their output into that layer of the PDF meant for the text itself, not its presentation.
If you are generating a PDF with text you can render a string with spaces and let the glyph layout sort it out, or render individual characters, or draw those characters by hand and use the invisible font trick (because your font is not licensed for embedding). It’s not that you’re using different conceptual layers of the PDF, you’re just choosing how to render your content.
Accepting a potentially inferior machine-readable plaintext when copy and pasting is the price we pay for having something like that available.
\usepackage{newtxtext}
\usepackage{newtxmath}
for font setup.1. https://resource-cms.springernature.com/springer-cms/rest/v1...
FWIW, for non-math, single column text, LuaLaTeX + plex-otf [1] is my current favourite combo. Reads well both on screen and on paper. But if you are heavy on math, you will need to setup a second font to replace CM in the math formulas. You can also scout the top conferences/journals in your niche (i.e. where your prof. publishes) and pick a template you like. The templates are typically linked with every CfP, and you can expect that they will have worked-out the common cases for their field.
> It's so good-looking that some scientists do research just so they can write it up in Computer Modern.
It's more like "undergrad students use it in their papers because they don't know better". The only Computer Science publications I'm aware of that still use CM are the Springer LNCS/LNAI series. Which also happen to still use a template optimized for printing the proceedings as books. And AFAIK, these templates are universally hated and considered archaic and outdated: They look bad everywhere (screen, A4 printout, letter printout) except the Springer-printed paper volume.