markdownWeb
20 points by matts
20 points by matts
I think it's a fun idea and more practical than the truly sparse gemtext of Gemini, but I suspect you'd still run into limits too often. I've found I often embed raw HTML when I blog with Hugo or use short codes like figure. My html base template needs things like a link to my RSS feed for auto discovery (although I'm hoping we can standardize feed menus as a replacement for that).
I've seen a couple RSS feeds embedding Markdown instead of HTML, which makes a lot of sense if you write in Markdown anyway and the feed reader is going to apply it's own style.
I'll suggest adding <link rel=alternative type="text/markdown" href="..."> to your HTML so people can auto discover markdown on sites that support it. I think I saw some docs sites doing this (especially for agents to read).
I've found I often embed raw HTML when I blog with Hugo
I can get farther with reStructuredText (not in the Markdown spec: actually having metadata in the file like every other creative work format, summary/details, abbreviations, callouts, description lists, table captions, figures, attributions/citations for quotations, footnotes). I found one case where I needed straight up raw HTML (embedding a certain SVG), & I still do a fair amount of post processing. All this to say is we lose so much of the richness & semantics HTML provides by stripping things down to dumber & dumber formats—for both humans & the robots (if one cares). A huge part of the problem is all the gunk added to the markup: ads, 4000 Tailwind classes. With the more modern advancements in CSS/SVG, we don’t need nearly as much JavaScript or 80% of the hacks still floating around there that have duplicate elements, tons of wrappers, & so on. HTML is a fine format as is.
w3m is out there rendering HTML pages just fine in plain text (& is subjectively easier to read than Markdown). I wish we were targeting TUI browsers instead—where I have long suggested this as a coarse sanity check that your site is easy to crawl & easy for screen readers.
HTML is a fine format as is.
Agreed. I haven't assembled a real web page since the 20th century, so the modern stuff, from CSS on, goes way over my head. I judge in part based on demos and competitions. I rather miss the competitions for who could do the smallest web pages...
Random associated example --
Whereas with JS these days, there are no effective limits. You can embed full-function rich apps in pages; this is entirely normal. You can embed browsers in those apps to make them standalone, at horrific cost. Balena Etcher is my default image writer app and it's 200MB. I have used multiple entire OSes that were much less than 200MB. I have installed and run OSes that were less than 2MB in production. Hell, I used an OS whose working set was about 2kB, and I used it for some years.
You can run a VM in a web page, and in that VM, run an entire desktop OS, and in that OS, run another emulator if you want. It's not a markup language, it is an entire computer platform -- one with a bad, loose, incomplete, and ever-changing spec.
We don't need Gemini. We just need a movement of web sites that completely ban JS and celebrate it as a badge of pride. No cookies, no scripts, no worries. What's left is more than enough for a rich interactive web.
Hell, I used an OS whose working set was about 2kB, and I used it for some years.
Which one, out of interest? I'd guess something ROM-based embedded
CP/M. I'm old, and my first computer with a monitor (as opposed to a TV set) was an Amstrad PCW9512, one of the last ever DR CP/M-80 machines ever made, in about 1988.
Although it has 512kB RAM, of that, only 64kB was available workspace, and the rest was a RAMdisk. CP/M 3 unloaded most of itself into the RAMdisk when an app was running, leaving about 3kB of resident code.
I was going down by rough orders of magnitude (or multiples thereof) and 2kB was a lot closer to the reality than 20kb. :-)
I agree. When I created my static site (markdown based) I had the idea that I would set the world aflame with my white-hot rhetoric alone. Almost immediately I found I wanted fancy formatting or constructs that are either very difficult or impossible with markdown.
Most recently I have added a simple embeddable photo album to my mostly text blog. It’s nice to have the option.
No shade on those who yearn for a return to the text heavy web, though.
HTML is a publishing format. Markdown is a family of mutually incompatible and often ill-defined authoring formats. It’s quite unsuitable for this purpose.
The allure of writing in Markdown has always been simplicity, and to an extent, "progressive enhancement". (I'm unsure if this is the correct term here, I mean the following.)
Many Markdown renderers allow certain HTML elements, and LaTeX math mode to be interleaved with Markdown syntax, which alleviates most of the restrictions one can feel imposed upon them when writing Markdown. Importantly, if no need arises for such additions, one can ignore these extensions to the language, and keep to the minimalistic parts of Markdown.
The problem is that this extension of Markdown not standardized, and is an incohesive amalgam of three different markup languages. A language that achieves roughly the same goal as the Markdown+HTML+LaTeX monster, is Typst.
Basic markup in Typst is almost exactly the same as in Markdown, unlike HTML and LaTeX, which have an uncomfortable amount of boilerplate (i.e. bold versus <b>bold</b> or \textbf{bold}). Simple styling, usually achieved through embedded HTML in Markdown is also simpler, and is more cohesive in Typst. Math mode is also nicer in Typst, than in LaTeX-in-Markdown.
Point is, in my opinion, that Typst fits the "progressively enhanced markup language" niche the best, which is only approximated by Markdown, and barely poked at by HTML and LaTeX. Typst would fit the idea of the post perfectly, even more so than Markdown.
I've had the Idea to make a "Typst browser" by forcing set page(width: <viewport width>, height: auto) and a greedy line breaking algorithm. Easier said than done of course.
Why greedy? Its only benefits are stability during editing (inapplicable) and performance (almost never enough to worry about).