BTW, if OP is reading this, I recommend having the baseline in your plots (e.g. std::deque) as the relative 100%, that way the performance improvement is clear.
This might be rendered moot by native microscaling support in Blackwell (MXFP). They've manually done a coarser-grained version of that for Hopper, but with full FP32 scaling factors.
These are very good and high profile public demonstrations of where $NVDA's moat is: that GPGPU is very flexible and you can program to do a lot of stuff that makes perfect sense but wasn't in the mind of hardware vendors.
Now, if you predict the future to eventually converge on more and more dedicated hardware support, to the point that there's no more software optimizations like these, then the so-called "CUDA moat" breaks.
To stay in this game, NVIDIA is breaking down their own moat :p
Gravity's Rainbow is just a shadow of Pynchon's best work by a large margin, Mason & Dixon. I can't recommend it highly enough. It's probably the best novel I've ever read.
Arabian Nights has been on my list to produce for SE for a couple of years now, but its sheer size is imposing. I’ll probably do it in the not too distant future though.
Whoa, SE looks incredible. Thanks for your work on that!
Are there any plans to support non-English ebooks as well?
Edit: Regarding non-English ebooks, I was thinking about books like "Der Vogelflug als Grundlage der Fliegekunst" (Birdflight As The Basis Of Aviation) by Otto Lilienthal (https://www.gutenberg.org/ebooks/54565). It's a fantastic book with nice hand-drawn illustrations, and it would deserve being presented/typeset in a beautiful way. Currently available ebooks are mostly bad.
Sorry, no. Like I said in another comment, a large part of what makes SE good is our manual of style, which is really just applicable to English works. If you want to use the toolchain to produce a novel in another language feel free (removing our logo and name, of course).
Nearly two years, but I took a bunch of time out to work on smaller pieces. The biggest problem was that Gutenberg had only transcribed about a third of the footnotes, so I spent a long time adding the remaining ones back in.
I had a chat with Phil after I finished, and he sent over a list of transcription problems with Gutenberg that I’d missed which was very kind. But apart from that, no direct collaboration.
For those who loved the Andrew Lang rainbow-color fairy tale books, Lang also published a volume of The Arabian Nights, not a translation but a recounting of selected tales. I encountered the Richard Burton commodious 3-volume set as a child. It's amazing that nobody at the time thought to proctor my reading choice, given the racism, misogyny, salaciousness, naughty illustrations, everything delivered in such a matter-of-fact tone and just laid out there. To read it cover-to-cover is actually not terribly fun. There's lots of little folk tale snippets, fables, poetry, and Burton footnoted the hell out of everything.
This question comes up a lot. The source to our production pipeline is GPLed and freely available,[1] but the biggest part of why we produce good work is that we have a high quality manual of style.[2] Unfortunately, that second part is very specific to English, and that’s the difficult part to replicate for other languages.
From a brief look, the typography
section of the manual is definitely language specific. Different written languages often have a much different typographic convention; depending on the language, different countries using it may have major or minor differences in conventions. And of course, there are different interpretations of the convention; they've included by reference a specific version of the Chicago Manual of Style. For another language, you'd need to at least need a different exhaustive manual to reference, as well as changing or reviewing the specific guidelines.
That's work that really needs to be done by a fluent, literate user of that language, hopefully with background in that language's literature and experience in copyediting, and familiarity with publishing. It's not really work you can demand of someone who did a good job (I assume) of it in English; they won't do a good job of it in another language without deep experience in that language. Developing and publishing the works in the language also needs to be done by people fluent in the language.
The example of the English version can be a guide for other languages, and there's of course room for collaboration on software between languages, but asking the English language project to expand to other languages is unlikely to get good results unless the developers also are fluent in those languages.
When we edit, we’re literally building a standard ePub3 file, which natively uses XHTML as its document representation. The pipeline then produces alternative versions of the same file. We could work in LaTeX, but it would reduce our contributor count (more people know XHTML than LaTeX) and we’d need to transform it anyway, with the potential of introducing new bugs.
You seem to have confused 1421 with 1491. The latter is generally considered to be a well-researched book while the former is, as you say, merely a grand tale.
BTW, if OP is reading this, I recommend having the baseline in your plots (e.g. std::deque) as the relative 100%, that way the performance improvement is clear.