9,983 karma · joined October 22, 2010
My book on LaTeX: https://preppylion.com
Writing fiction (and occasionally poetry): https://dahosek.com
⸻
1. Worth noting two key differences between the Mexican and American car buying experience: First, prices are fixed. There’s none of this negotiating with the dealer about the price or upselling you on undercoating stuff. You can look on the website and know what the price is. Second, instead of sales tax, Mexico uses VAT to achieve the same purpose. As a result, the price you see for a product is going to be the actual price you pay walking out the door and not the price before sales tax (at my current residence, the total sales tax is currently 10%). As a consequence, some things that might appear to be slightly more expensive in Mexico, depending on where you live, may actually be slightly cheaper.
But I am reminded of how during my engagement 24 years ago, my future father-in-law raised an issue of being able to determine whether they were getting the full amount of sandpaper on large rolls that they were paying for. I was able to simplify the question a bit to one that treated the rolls as if they were simple concentric rolls of a specified thickness and from there could turn it into the good old Gaussian sum formula times 2π to get the length. The engineers working for the company came up with the same solution, but instead of using n(n-1)/2 they did the summation with multiple rows in excel.
The weird thing was that putting my kids’ names in (they are 12 and have no on-line presence), the system hallucinated fictional versions of them that matched their interests (my daughter a singer/actor/artist, my son a software engineer). My ex-wife, who has a published computer book to her name, on the other hand, was hallucinated as four different activists in different areas of interest.
I didn’t know about the field that used to be in La Grange, whose location is now a gravel pit (which, combined with another one on the other side of Joliet Road is responsible for the closure of a stretch of historic Route 66 although the gravel pit operators insist that despite quarrying to within a dozen feet of the roadway on either side, they aren’t responsible for the subsistence of the road.
They haven’t brought up bridges and weight limits yet so I can only assume they still believe that.
Now the bugs that get ignored for new features cause bad results AND bad performance.
In college [2], when I wanted to quote some texts from Exodus in Hebrew in a paper that I wrote, I ended up avoiding the issue by hand-reversing the letter order and manually breaking lines. 8 bits is insufficient to cover all the possible combinations of letters and vowel markings so the font didn’t include any vowel markings and only did dageshim for בּ and פּ if I recall correctly.
⸻
1. As an aside, it would have been really nice if Unicode provided a R-L mirrored Latin alphabet to make it easier for monolingual developers to grasp the complexities surrounding mixed directional typesetting. I suppose it could still be added, although Unicode tends towards conservatism on adding additional characters.
2. This was 1990, well before Unicode in the era of a hundred or so 8-bit character encodings, most of which were not implemented widely. I also had to type the text using the arbitrary ASCII-Hebrew mapping of the font I was using which, among other things, led me to discover that letter frequency in Hebrew is much more uniform than it is in English.
The pdftex engine is pretty much a dead end these days and I would only recommend its use for compiling legacy documents.
That said, the biggest problem is nothing to do with the source code of TeX. The change file mechanism is pretty straightforward and there have been tools for decades to allow application of more than one change file against the source, although with the standardization on web2c in the build process as well as better cross-platform C compilation in 2026 vs 1982, there isn’t the proliferation of platform-dependent change files that there were in the 80s when people were compiling on Pascal compilers that supported different subsets of the language.
But as I was saying before I got into that digression, the source language isn’t the issue with TeX so much as the basic architecture which is highly coupled to the limitations of computers in the late 70s/early 80s when even 7-bit ASCII couldn’t be assumed to be consistent between systems¹. As much as I enjoy writing TeX macros and can do wonderful things with them that most people would consider dark magic, it’s a cursed way to do programming and has no parallel in any other programming paradigm.
⸻
1. The SAIL platform at Stanford where Knuth did the initial work, for example, had ↑ in the code space ASCII designates as ^, and IBM mainframes all used EBCDIC which has the complication of having | and ¦ as two separate characters both of which were typically mapped to | in EBCDIC to ASCII conversions with the reverse conversions arbitrarily choosing one of the two characters so that there was no guarantee that you’d get the expected character in your text file conversion² or your ASCII terminal controller.
2. Which is yet another reason why non-Unix operating systems would have distinct text and binary modes for opening files.