5 ms·
LaTeX is not equivalent to PDF, though that is one publishing format it supports. HTML lacks numerous features which a first-class document-specification langu
by dredmorbius 5y ago
LaTeX is not equivalent to PDF, though that is one publishing format it supports.
HTML lacks numerous features which a first-class document-specification language should have, including grid layouts (only very recently possible), footnotes and sidenotes, and formulae.
The promise of LaTeX is that documents could be defined strictly in semantic terms, though my belief is that this would last for approximately 37.229 minutes after such a proposal actually hit the Web.
The underlying failure of HTML is that it is runtime compiled, not precompiled. This makes things far easier on authors and publishers, and far worse for readers. In the early days, the former mattered in order to incentivise content. Last I checked, incentivising content is no longer the Web's principle problem.
I've also been leaning toward LaTeX as a document speification language for hypertext systems, though I don't believe that alone is sufficient to fix the Web's ills.
- freemint 5y agoHow would you support multiple screen resolutions or even resizing windows with precompiled layouting? If layouting (an computationally expensive step) is done at "run-time" what would precompiled even mean?
- dredmorbius 5y agohttps://news.ycombinator.com/item?id=29372589 https://news.ycombinator.com/item?id=29372589 https://news.ycombinator.com/item?id=29372490 https://news.ycombinator.com/item?id=29372490
- DaiPlusPlus 5y agoWhat do you mean by “runtime compiled”, exactly?
- dredmorbius 5y agoWith LaTeX, the document creator must compile the document, through a fairly persnickety processor (latex, tetex, or an equivalent). Whilst that may still pass poorly-structured documents and result in poorly-formed output, straight-up illegal syntax won't make. HTML has no such requirements. There's absolutely nothing stopping you from posting that in the first place. Throw something at a browser, and it will try its damndest to ingest it --- that's the "runtime compiled" element of the Web. (It's not a perfect analogy to software compilation, though it can get surprisingly close.) Essentially: the Web lacks any editor role. That's long been touted as a benefit. At scale, however, and over time ... it becomes problematic. Moreover, the commercial Web has a selection process and corresponding evolutionary path which has come to be seen as less than optimal for those seeking high-value, high-relevance content. It is in fact hostile to such content, on multiple bases. Again, LaTeX alone won't fix these problems. It addresses a few issues of structure. The concept of a post-authoring compliation state (ironically itself somewhat present in many web content-management systems, but not oriented around the document or content itself for the most part, but rather branding, advertising, and surveillance instrumenting) is also somewhat attractive but ... problematic. A discovery-mechanism scoring penalty might help (and Google's certainly applied that in other areas).
- DaiPlusPlus 5y ago> Moreover, the commercial Web has a selection process and corresponding evolutionary path which has come to be seen as less than optimal for those seeking high-value, high-relevance content. It is in fact hostile to such content, on multiple bases. That aspect has absolutely nothing to do with the technical format of a document.
- dredmorbius 5y agoThat's a large part of my larger point. It wasn't, however any aspect of the question you'd asked, and I'd answered. That said, and despite some quite strong semantic elements to HTML (and HTML5 especially), and the semantic/presentation separation of HTML/CSS, what we're getting, what seems to be encouraged by, and what the adtech-profiting browser vendor and driver of Web browser development seem to be encouraging, is not in fact well-structured, meaningful, high-value, high-relevance documents. You're absolutely correct that the core of the problem isn't the technical format. But the technical format's become infected by that core problem.
- ttybird 5y ago"must"? A web4 browser would probably use a "runtime compiled" implementation. "Whilst that may still pass poorly-structured documents and result in poorly-formed output" - this by the way happens much more often with LaTeX compared to html in my experience.
- dredmorbius 5y agoA LaTeX document is virtually never directly consumed by a reader. It's first converted ("compiled") into some consumable format. Typically PDF/Postscript, though there can be numerous others. You seem to be unfamiliar with this aspect of the system?
- garbagecoder 5y agoWe don’t see html raw either dude
- zozbot234 5y agoFootnotes and sidenotes can be realized as <aside> elements and styled/scripted to appear as actual footnotes on print media. Formulas are supported via MathML.
- dredmorbius 5y agoNeither are native first-class elements of plain HTML.
- ttybird 5y agoNor a "first-class" TeX element either. \footnote is just a macro.
- dredmorbius 5y agoWe're discussing LaTeX. TeX itself is a set of typesetting primitives. LaTeX is a set of structurally-semantic, document-oriented macros built on TeX.
- tasogare 5y agoLatex is not semantic, the fact it's using macro (which are factoring function calls) says it all. There is some degree of separation between content and presentation, but that's it.
- dredmorbius 5y agoLaTeX as designed is generally semantic (formatting is left to the applied style), and whilst HTML5 is in theory reasonably semantic, in practice, LaTeX tends to be used far more semantically than HTML is. Some of those reasons are technical, though as noted elsewhere in this subthread, economic and other factors seem more dominant, and I severely doubt that LaTeX on its own will address the broader scope of issues raised in TFA.
- 5y ago
- dnautics 5y ago> The promise of LaTeX is that documents could be defined strictly in semantic terms, though my belief is that this would last for approximately 37.229 minutes after such a proposal actually hit the Web. I mean, that already failed for LaTeX. To me it's kind of an unwieldy pile of wierd imperative imports. I did write my thesis in it, but for the most part it was "smash these imports together, pray for the best, if it doesn't work, try a different collection of imports, don't bother trying to fix your imports, settle for "least bad" -- which, of course, was better than MS word". I used to do my resumes too, with the same spray and pray feel. Now I just write a markdown file, and anyone that cares that the resume is poorly formatted I probably don't care to work for (many places sanitize resumes to a single format anyways, i suppose for non-discrimination purposes). Honestly, even though I myself can't use CSS effectively, what little bit I can use feels like CSS is converging to that declarative-layout-that-is-separate-from-document-contents philosophy that LaTeX tried to do, with the major distinguishing point that LaTeX had a huge "start with sane defaults" selling point, and CSS most definitely does not start with sane defaults.
- infogulch 5y agoWhat would sane defaults for css be?
- dnautics 5y agoMaybe I spoke too soon -- Thinking back (and I could be wrong about this) but the "top" of the style sheet cascade is supposed to be defined by the browser? So I guess it's the browers' responsibility? I guess the point I was trying to make is that if you just type only non-layout LaTeX it looks reasonably good, yeah, it does format it with super-wide margins (shrug), but if you do that with html you get mouth spiders.
- dredmorbius 5y agoI'd like to see something far closer to my "Motherfucking Website" variant: https://codepen.io/dredmorbius/full/KpMqqB https://codepen.io/dredmorbius/full/KpMqqB There are a few bits of that I'd fiddle with, but the idea of defining margins and avoiding text that runs flush to gutters, as well as defining most of the whitespace in rem & em units rather than pixels or points, is a big part of it. Another alternative would be a stock set of document types for which users could choose from predefined styles. The document would specify the doctype, the user the styling. That could include various branding or simiilar components, but they'd be reasonably minimal. The ever-encroaching headers, footers, sidebars, floating interstitials, etc., of the modern web really need to go DIAF.