WordGrinder VS Markdown by DaringFireball

There are some people trying to recreate the Wordstar experience, like this one, and they supposedly were great and simple for writing long-form content (it was before my time, so I have no experience with it). Source: 10 months ago

WordGrinder. It's great for distraction-free writing, and can output Markdown or troff. It's a great tool for getting words down, but its otherwise pretty limited (which I think is one of its strengths). When I need to print or generate a PDF, I have a little script. Source: 12 months ago

For word processing there's WordGrinder, which is in the repos for many distros (in Fedora: dnf install wordgrinder). Things like LaTeX and Groff are for typesetting, which I don't view as the same as word processing. WordGrinder is more like the classical DOS word processors (e.g. WordPerfect 5.1). Source: about 1 year ago

I have a word processor I wrote (https://cowlark.com/wordgrinder) which is mostly written in Lua, with hardware-specific stuff in C, and while this works extremely well, I'd very much like something with stronger typing. There's a possibility I'd be able to just drop in Luau and get it, plus some performance benefits. I'd need to reimplement parts of the standard library due to Luau having dropped things like the... Source: over 1 year ago

I really like using WordGrinder, a terminal-based text editor. It has pretty much only the features I need and otherwise gets out of the way and let's me write. You can check it out here if you're interested. Source: almost 2 years ago

In today's fast-paced tech world, giving effective presentations is crucial for conveying complex ideas and engaging audiences. While Markdown has emerged as a popular lightweight markup language for creating rich text documents, its use in creating dynamic, interactive, and visually appealing presentations can be challenging. This is where Marp comes into the picture - an open-source Markdown presentation app... - Source: dev.to / about 2 months ago

It's just CommonMark, Gruber was ticked off enough that he declined to allow them to use the term Markdown at all. Alone among the variations, or nearly so, he's fine (as your link indicates) with Git-Flavored Markdown. The thing is, they didn't fork it, they decided to "standardize" it. John Gruber had already published a Markdown standard: https://daringfireball.net/projects/markdown/, and a reference... - Source: Hacker News / 2 months ago

Aha that's just an inline footnote, we support both in Supernotes. So you can quickly write ^[Name of Reference] (that will auto assign it the number 1 once rendered) rather than [^1] ... [1]: Name of Reference. Footnotes aren't part of the original Markdown specification (https://daringfireball.net/projects/markdown/). - Source: Hacker News / 2 months ago

Markdown is a text markup language. It's widely adapted. For example, github repo's will detect the readme.md file in the current directory and display it below. - Source: dev.to / 4 months ago

Note, that this file is a Markdown and YAML file at the same time, and as such human- and machine-readable, if the fields are filled carefully. - Source: dev.to / 5 months ago