Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our community
Peter J. Mello's Experience
PersistentEuthenia's Experience
RickZeeland's Experience
TrustingAgon's Experience
Peter J. Mello's Experience
ReliableRaediengiedte's Experience
Top Pro
•••
Top Pro
•••
Top Con
•••
While I do like the fact that Markdown has achieved a breadth of utilization across various tech-related or -adjacent domains to become fairly ubiquitous, I firmly believe that most, if not all of them, would objectively be better served by almost any other markup language that isn't overly intricate, especially if they were governed by a single, canonical standard whose evolution was guided by a democratic/meritocratic organization. Markdown continues to have far too many "flavors" and a feature set which never seems to grow meaningfully or consistently. See More
Markdown is a poor choice compared to other lightweight markup languages. See More
Easy to read and understand and widely supported, Notepad++ has a plugin for Markdown. See More
Very simple and clear, yet incredibly powerful syntax. Especially easy management of lists and checkboxes. Very powerful support of tags and more complex attributes (especially "properties", which allow for database-like functionalities). An incredibly useful and powerful tool: Org-babel, which is a metalanguage. Add to it the power of Emacs and all its packages... See More
As both a software developer and an 18-year+ contributor to Wikimedia projects like Wikipedia/WikiBooks/WikiVoyage, I've written a lot of markdown...a LOT. It gets the job done, no doubt, but the only thing it has going for it is the first-to-market advantage. The specification (Commonmark) is ridiculously resistant to evolving, especially for a widely-adopted standard, which has led to (by my count) no fewer than 32(!!!) different implementations of it in which almost always tweak aspects of it, precisely because there are so many features that are central to usability that the spec. writers simply refuse to address. It sucks. A couple years ago I ended up working on a project hosted on a GitLab instance that required me ending up having to really dig into the documentation, and in the process encountered their advocacy for writing documentation in AsciiDoc format instead. I must've been extra fed-up with markdown at the time, because I jumped at the chance to use a different syntax, even if I had to learn it from scratch. I know I wasn't even two hours into the process of documenting my work when I stopped typing mid-sentence and sat back in my chair, mouth agape, and thought to myself, "Holy sh*t, this format has everything I've always wished markdown offered, AND a bunch of handy features that I hadn't even thought to want to use! I have no explanation why it's so lightly used, because ever since I leap at any chance to use it in place of markdown. Admittedly the syntax isn't as bare-bones simplistic, so it requires some practice, but the output is of such higher quality by comparison, I have no doubt more people would use it if it had broader support. Sadly, I can't think of any major services that support it out of the box other than GitLab, but if you do any document creation there or somewhere else that will parse it, I implore you to try it out for yourself and see for yourself just how much of an improvement it is. See More
I've been using Markdown for the past 11 years for various needs where the content is more important than the looks of the output. Finding AsciiDoc and its rich list of functions and clean syntax has made me hate Word even more; finally a way of writing documentation that doesn't hurt me to my soul! I'd even go as far to say that I'm actually enjoying the process with AsciiDoc! See More
The AsciiDoc standard defines a number of metadata values which can be defined inside a document primarily for contextual purposes that aren't rendered in its standard output such as author, date, license, document title and version, etc. These can be especially useful when searching through a large number of files/documents or documenting the evolution of one as part of a larger codebase. See More
The whole reason that TeX -- and, by extension, LaTeX -- exists is to give people an easy way (well, for some value of "easy") to produce high-quality documents with properly laid out mathematical expressions and text in them. As long as you know the language (or have a reference sheet handy), you can include mathematical expressions in your document with little to no extra effort needed on your part. See More
LaTeX is single-threaded by design, since it must necessarily work sequentially to produce each page as it is laid out by the typesetting engine. This makes it dependent on the power of just one individual core in your multi-core computer setup and so migrating to a machine with more cores won't necessarily make your LaTeX documents build faster. See More