Hacker Newsnew | past | comments | ask | show | jobs | submit | thangalin's commentslogin

> What it can't do (as far as I understand): complex layouts, precise typography, embedded binary content, anything that needs pixel-perfect rendering.

Please see:

* https://impacts.to/downloads/lowres/impacts.pdf

* https://keenwrite.com/docs/user-manual.pdf

* https://keenwrite.com/blog/2025/09/08/feature-matrix/pdf/jek...

* https://keenwrite.com/blog/2025/09/08/feature-matrix/pdf/sof...

Those are Markdown documents typeset using ConTeXt. Except for Jekyll & Hide, I wrote them all.


> Although it sucks that markdown is not standardized

Does CommonMark count?

https://spec.commonmark.org/


I've posted my feature matrix elsewhere in this thread:

https://keenwrite.com/blog/2025/09/08/feature-matrix/

The matrix, which you can download, aims to provide an objective comparison. Any idea what features are missing, or can you qualify what makes the other text formats "better"? From my perspective, they are largely equivalent.


Can you quantify "much better"? I compiled a set of over 70 features offered by a variety of plain text formats:

https://keenwrite.com/blog/2025/09/08/feature-matrix/

Are many features missing from the list? From what I can tell, objectively, plain text formats offer largely equivalent functionality.


Does anything need all those features though? If you need more than headings, bold, italic, quoted text, and code, you should probably be using HTML or Latex or something. So a better goodness-of-fit function would be is it easy to remember/use, and is it non-intrusive inline with the text?

There are those that have well defined extension points (e.g. TeX, rst), and those that are ad-hoc, of which the best example is markdown. TeX, via packages and wrappers, can do practically anything. rst has directives (blocks) and interpreted text (inline) which can also effectively do anything (along with substitution references which are more macro-like). Specific "interpreters" (for lack of a better term) which you link to naturally have specific features by default (and some are more extensible than others e.g. pandoc which when writing out LaTeX lets you embed LaTeX in the markdown, so "markdown" in this case is turing complete).

I think if you define "better" as having well-defined extensibility to enable multiple implementations (i.e. not ad-hoc things pandoc lets you do), then rst (which can be transformed into XML as per https://docutils.sourceforge.io/docs/ref/doctree.html) would be "better" than markdown.


The original Markdown has fewer features than listed for the more advanced formats in the table. Hence if someone uses reStructuredText it is more precise than just saying “Markdown” because Markown could refer to anything from the original minimalist featureset to the vastly extended format supported by pandoc if given the appropriate CLI arguments.

Some text-based formats have more options for tables e.g. alignment of columns (it may help with numbers to right-align them) or multirow/multicolumn options. Some formats support definition lists (corresponds to <dl> in HTML) - a feature which I often find valuable but was not included in the original Markdown IIRC.

One advantage of using a text-based format is that it can be exported to either LaTeX or HTML and Markdown seems to prefer the HTML output by explicitly supporting inline HTML as an escape hatch for more complex constructs (e.g. tables with rowspan/colspan). In addition to often not being supported for a non-HTML export-type it also hurts the WYSIWYG experience when reading the file like plain text.


> For example while docbook may have some technical

https://keenwrite.com/blog/2025/09/08/feature-matrix/

I wrote the feature matrix to objectively compare plain text-based documentation formats. How do DocBook's features compare against Markdown?


My brief, illustrated history of Microbial Mats (p.10) to Multicellular Eukaryotes (p.13) may be of interest:

https://impacts.to/downloads/lowres/impacts.pdf


This is quite well made, thank you for sharing. I appreciate the relevance and knowledge section on each page's subject.

Standard Ebooks produces exceptional quality documents. Here's my comparison against similar projects:

https://dave.autonoma.ca/blog/2020/04/11/project-gutenberg-p...


Somehow I stumbled across your post/series back in 2020, and that was my first introduction to Standard Ebooks. Now, these years later, I've produced >60 SE titles, and read many, many more. Needless to say, I'm greatly in your debt! :)

> started in a reasonable amount of time

A hasty generalization with a little confirmation bias, perhaps?

    $ time keenwrite.bin --version
    KeenWrite version 3.6.5
    Copyright 2016-2025 White Magic Software, Ltd.

    user 0m0.329s
From Claude:

> It's worth noting this is a common perception about Java, and there's some historical truth to it (especially with Swing desktop applications from the 2000s). However, the absolute statement "no Java app... ever" is the fallacy - it's an overgeneralization from limited personal experience to a universal claim.


It’s not a generalisation. I am a specific individual relating my own experiences. I have no idea what your app is and have had zero reason to use it.

> There is no way to get your jar + the vm into a binary.

My text editor, KeenWrite[1], offered binaries for Linux, macOS, and Windows. The Windows binary was axed due code signing costs and requiring third-party builds, rather than any technical issues with cross-platform packaging.

One way is to create self-extracting executable binaries using a tool such as warp[2]. I've built an installer script[3] (install.sh) to create platform-specific launchers. Running `time keenwrite.bin --version` on Linux shows 0.327s; after the first run, subsequent launches are quick.

[1]: https://keenwrite.com

[2]: https://github.com/kirbylink/warp

[3]: https://repo.autonoma.ca/?action=repo&repo=keenwrite.git&vie...


> I think it’s little appreciated that high CO2 levels cause cognitive impairment

Have you been telling representatives? Here's a letter I wrote to mine:

https://pdfhost.io/v/bRJEGptatL_climate-change


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: