Earlier quoted context omitted.
I had to write a paper with it. I found it so horrible that I ended up not writing the paper (on a very interesting topic) and failed class. I just assumed the professor was nutty and kept onto some weird niche software.
Nope, the professor was requesting that you use the standard typesetting software. Some of your classmates might have to write many papers, and hence it's good that they start learning.
The price of a messy codebase: No LaTeX on the iPad
181–190 of 247 posts
Re: The price of a messy codebase: No LaTeX on the iPad
#182Re: The price of a messy codebase: No LaTeX on the iPad
#183I don't know, maybe the author is trying to do something with the iPad which is simply not supposed to do. The iPad is beautiful, pleasant to use etc. but writing a book on the iPad is maybe not the things one does. I use my tablet to write — quite a lot — way slower than on my regular keyboard, but with time to think. Everything is in text files, synced to my desktop where the typesetting is really performed. Writin…
I completely agree. I understand that tablets are a wonderfully portable device but you can't expect to get 100% desktop functionality. Sometimes you have to find the limit of your software/hardware. I don't own an iPad, but is there git or the like? If so syncing and keeping track of changes would be simple.
The point is that there does seem to be a software limit, but there shouldn't need to be a particular limit there. There's certainly not a hardware limit, since an iPad can run circles around almost all of the computers of the era when LaTeX was written. Unless you believe that the TeX system represents an almost magical, once-in-a-lifetime, impossible to replicate achievement in software engineering, there's shouldn't be a software limit either, but the code base is so complicated that there does seem to be one.
Re: The price of a messy codebase: No LaTeX on the iPad
#184Earlier quoted context omitted.
I assume he meant that core TeX (the part written ages ago by Knuth) is in effect bug-free. However you do have a good point that one effect of core TeX being ancient and not really updated is that, in practice, what people actually use is TeX plus giant macro packages whose size is bigger than TeX itself, and those are certainly not bug-free. It's at least plausible that a rewrite wouldn't lead to more bugs total, i…
Nobody uses (Knuth's) TeX anymore. They use PDFTeX, XeTeX and LuaTeX. None of these are as stable as TeX, but in practice a whole lot better than most other software I use.
Re: The price of a messy codebase: No LaTeX on the iPad
#185The price of a LaTeX rewrite would be even higher: incompatibility. If one tries to rewrite TeX, the problem gets much much worse, since TeX is, for all intents and purposes, bug-free. A new implementation will certainly not be. Joel Spolsky said it very well http://www.joelonsoftware.com/articles/fog0000000069.html I disagree that the current situation is LaTeX developers' fault. TeX and LaTeX are complex pieces of…
> For whatever reason, they cannot allow applications to use the existing capabilities of the underlying OS. This goes against the Unix mindset; of course there will be unpleasant consequences, but one cannot hold Unix mindset responsible for these. Using the native capabilities of the OS in the sense you mean - allowing TeX to use its ancient, hideous bitmap font system, goes against: - Unix philisophy - do one thin…
TeX's original goal of 'allowing anyone to create typeset documents'
Actually, according to this interview[1], speaking of the very first version of TeX, "I should mention that I had no idea that I was designing a typesetting system that anybody else in the world would ever use, besides me and my secretary. My idea was that I would teach Phyllis, who was my secretary for almost 20 years… So Phyllis and I were going to be the users of this TeX system. … I tried to design it just good enough to do my books and no other books."Even with the released version, I don't think TeX was ever intended to be the last word on typesetting; it was simply his best attempt at a decent markup. He then froze the features so that previously typeset books could be corrected and reprinted using the same source. He left it up to future programs to innovate.
Re: The price of a messy codebase: No LaTeX on the iPad
#186One real issue is that most users' LaTeX environments are highly customized and tweaked to our own liking. Even if it weren't absolutely nuts to put every-package-and-extension-known-to-man inside a iOS binary, it still wouldn't be right. Like, what if I want LaTeX2HTML (I've never not had to highly tweak this)? What about my snazzy custom fonts? That bibliography style that only one journal accepts and requires thes…
Re: The price of a messy codebase: No LaTeX on the iPad
#187Re: The price of a messy codebase: No LaTeX on the iPad
#188Has Apple started allowing non-trivial Turing complete languages into the App store now? Unless I'm mistaken LaTeX would be rejected out of hand no matter how much you clean it up because it is an interpreter.
[1] Codify: http://itunes.apple.com/us/app/codify/id439571171?mt=8
Re: The price of a messy codebase: No LaTeX on the iPad
#189Earlier quoted context omitted.
Virtual machines are generally prohibited by the guidelines as well. (Exceptions exist for things like script interpreters, which need to be present for some games to run, e.g. Lua.)
You can't do very much within those guidelines, can you?
Re: The price of a messy codebase: No LaTeX on the iPad
#190Earlier quoted context omitted.
You think Donald Knuth has made a career for himself out of being able to right 'bug free code'? Really? He's made a career for himself out of being an extremely creative computer scientist and writing outstandingly scholarly books about programming. Far from marketing himself as producing bug-free code, he has published articles entirely devoted to the history of bugs found in his software. (As for the bits that tur…
Of course not, it's hyperbole to illustrate the point. In the specific cases of Qmail and TeX, the 'bug free' aspect of it however is overblown and a marketing gimmick. It's not that hard (given enough time) to make something bug free, it's a whole different thing when the software needs to evolve at the same time to meet the (changing and expanding) requirements of actual users.