In defense of Markdown tables: Markdown - and by extension, its tables - was originally designed to be human-readable in plain-text form (and I think it still does that pretty well, regardless of flavor). ADoc tables are not recognizable as such if you don't already know the syntax.
All syntax problems are either personal preference or solvable with simple (and common) extensions. Markdown flavours, while different, are all similar enough it causes no problems unless you are using advanced features. All the rendering stuff at the end (syntax hiloghting, PDF format, etc) is the job of the renderer, not the format. The only reason it’s “consistent” with ASCIIDoc is because there is only one tool to handle it.
@@lostsauce0When people talk about markdown being human readable in plain text, they don’t just mean that it is literally English language text. The point is that Markdown syntax should have the same visual implication even when it hasn’t been parsed. eg., a Markdown table in plain text looks like a table, with rows and columns. An Asciidoc table is just a list until it’s rendered.
@@quantumstormgames2741 You can for simple table, as having each element in a new row is not mandatory [cols="1, 1"] |=== | this | is a valid | 2 columns | table |=== When you need a complex table with vertical or horizontal span or sub-table, all of which is possible in asciidoc, than you're out of luck
@@w01dnick The original markdown spec has no tables, but that’s hardly still what defines what markdown is lol. GFM includes tables and that’s one of the most popular MD standards today. Besides, that was just one vivid example of what I meant. The difference between markdown’s readability and something Asciidoc is visible in basically every type of formatting element
@@w01dnick The point of the “15 competing standards” problem isn’t to say that whatever product was developed later is worse lmao its just saying that if people haven’t agreed on one solution, you probably won’t be able to convince them to. I didn’t know that AsciiDoc was created before MarkDown, but all that suggests is that if Markdown managed to become the predominant tool today, it’s probably better lol
@@quantumstormgames2741these two specs are not even competing. They serve different purposes. Markdown is obviously used more because it's more convenient for software developers to document their software in a simple and efficient manner (especially considering reading raw files via terminal via ssh). However Markdown is not meant to be used for bigg advanced research papers, books, improvised Jupyter Notebook replacements (look at Markdown Preview Enhanced, it's very powerful, but not always reliable nor consistent) etc etc. And this is exactly the role that AsciiDoc excels in. It's robust, consistent, doesn't have a million ways to do the same thing, opinionated, doesn't require you to install gigabytes of binaries (unlike say LaTeX) and still pretty readable in plaintext (again unlike LaTeX), and it's also usable on the web (unlike LaTeX).
Lost me at plugins, LaTeX, etc. Like jfc why does everything need to be a framework or abstraction layer now. Why can't people just write a standard that actually solves the problem instead of outsourcing it?
Yeah I'm not sure this is an alternative to markdown at all. It seems more like a document design tool & specification than merely a markup specification.
I think this is actually a good point. We should favour simpler solutions with fewer abstractions. I think plug-ins are okay here because generalised solutions tend to be more complex then specialised ones (since they must handle all cases). So I like having a generalised base for common tasks, but plug-ins that specialise where necessary
@@tom-delalande Agree. Plugins make sense for niche problems like embedding a videogame as it's not something that can be solved in a general manner and won't even work for most output formats. However something basic like diagrams or scientific notation is obviously something you want to be possible without worrying about if it's supported by your specific compiler or output format. Syntax doesn't even need to be nice, just give me a way to draw arbitrary shapes and glyphs relative to one another and provide a function syntax so third party libraries can use the standardized shapes API to implement whatever they want
I wrote my bachelor thesis in Pandoc Markdown, converted to latex, made changes at 5AM and then sent my thesis-final-final-final to the prof as PDF per e-mail. What a time to be alive. Looking back, I should've used typst locally using community VS Code plugins and such (I cannot upload my thesis on the typst site, as it contains NDA restricted information). Btw, the "sane" use of Markdown to create PDFs, sites and such, would be to use Pandoc and write filters for it, which can parse specific tokens to represent tables and other fancy stuff. (i.e. embedded files, the code snippets you mentioned, latex expressions, mermaid js integration (which is possible in some markdown editors!), etc.). The difference between AsciiDoc and markdown would be that the former has more "built-in", but technically... using pandoc... you get also these features "built-in" using filters (or easier: markdown editors like Typora). (P.S.: Jetbrains Fleet got recently Markdown Preview and they are working on AsciiDoc support for Writerside)
point 2 is already solved for markdown by pandoc. consistent markdown export to any format, supports inline latex if you want it, and output format is fully customizable. can even have one source markdown file export to pdf, html, and PowerPoint slides.
I just look to using markdown because my goal isn't to make a pretty document. It is merely because the formatting generally leaves a well understood document that you can follow along without being worried if it is being rendered or not by some fancy graphic renderer. The rendering is a bonus not required. I just feel this goes one step I've over. I mean everyone has different needs so I am not saying it is bad of course. I use the bare bones of MD mainly because I just want to separate sections and have documentation that gives me some clear intent or meaning without becoming superfluous and cumbersome. I know what is a list and can find and understand it without renderer. I know what headings are and what level usually denoting what layer I am in and so forth.
Probably just uses KaTeX under the hood, so why not go straight to the source ;). Seems like yet another standard, which doesn't accomodate everybody again anyways, so let's just hand-roll a renderer for whatever the situation requires, if it's special enough so that markdown won't suffice anymore.
Granted -- They've done a very thorough job documenting the standard, and covering a lot of potential use cases. But I feel like "complete" is an unreachable goal, because one person really needs LaTex rendering, and the next will ask "why doesn't it natively embed GeoJSON as a map?" (etc, etc). Markup languages can not really be feature-complete (HTML isn't either), so they will also never be fully consistent (HTML isn't either). Some website full of GIS geeks will offer support for GeoJSON, and before you know it you'll have different adoc flavors.
This looks awesome! I love markdown but the small inconsistencies does complicate things sometimes (and tables are painful 😅). I don't want more features, just more consistency. I'm gonna give this a try. Great video!
The look of exporting of a markdown being customizable is a feature not a bug. The raw plain text form of a markdown being readable is a design goal of markdown.
I mean, if I want this much control, I would just use an automatic tool to generate docs from source codes. The main point of a Markdown is that there is no special syntax, so you write it as if it was a plain text file, and is meant to be accessible even for non-programmers. The formatting is just cherry on top. When you start adding codes into Markdown just start to miss the points
@@_modiX I already did that, I just need some tips and workflow suggestions, also I'd rather be guided by someone who's already using it than to blindly do it myself. besides, it's more fun to watch a video than to read lol.
YESSS ASCIIDOC IS THE GOAT People don't seem to be getting that markdown's issue is it's complete and utter lack of content heirarchy or... organization in general beyond just headers. Or metadata. For more "longform" content asciidoc is wonderful, the point is that you can quickly (and reliably, which is huge) then convert it to PDF, e-reader formats, HTML etc. from that one source file.
With the exception of the table column per row syntax, Markdown can do all those things too. Source code highlighting, LaTeX formulas, diagrams, etc. all work in Markdown too. For more complex tables one needs to fall back to HTML code, which I think is the biggest problem with using Markdown.
You can do most of this already in iA Writer. There I do tables in my CSV editor (MarkupTable) and just hit save. It auto-updates the contents and I still have a nice UI to work with. I link and include sections by just reference the file names. A lot of markdown tools support this.
Seems nice, personally markdown together with padoc does everything i need. An features like diagrams are also available in the places I need them. Though nice to know of an alternative. Thank you for that concise overview ^^
The only reason not to use org mode is portability or you don’t use emacs. It is probably one of the most robust formats around. Neorg is getting quite good too. But I don’t use emacs anymore so markdown is good enough and very widely supported. Org mode is actually the only thing I miss about emacs.
Don‘t think AsciiDoc is an alternative, cause they got different philosophies. Markdowns: „The idea is that a Markdown-formatted document should be publishable as-is“ AsciiDoc: „Publish presentation-rich content from a concise and comprehensive authoring format“
I enjoy markdown a lot. When it comes to programming snippets I like the highlighting of different languages and usually make notes via comments in that particular language. But with tables I do have issues. I would love to scale them or to position them in two areas of view. In latex this is done pretty straight forward. With Latex there is tikz to draw nicely so if a markdown language supports this latex addon it's fine. Is there a way to build presentation in viewable landscape pdf form out of the box? There is a cool python program that takes a pdf an puts it into a presentation mode with highlighting and a dashboard to see all pages and suchs. It's called impressive but does not seem to be maintained any more.
I'll agree that Markdown tables suck. I don't use them. What I did with Parsedown and my personal wiki. was to use the ```fenced```` code blocks and the ```language...``` bit at the start. So if I want to include char delimited data, I use ````csv sep=|...```` using Parsedown to format each of the cell contents (i.e. bold, italic, link, etc), and then prevent Parsedown from further processing it.
More like a limited subset of Org. In a different accent. 😉 I find asciidoc to be a fine piece of kit, but I have a handful of fundamental disagreements. Nevertheless, adoc is still much, much better than markdown, which can frankly just f off and never return.
You mean I need to render it to read it ? I find it unreasonable as a replacement. I still open a lot of md file in vim or plain text cuz it's convenient. I don't want to go open another source file just to see what function was quoted. The video's great but asciidoc just is not imho.
Yes, those are two different things. AsciiDoc is for writing source files to be rendered somewhere while Markdown is just plain text that can be rendered if needed. One of the design principles of Markdown is, that it shall be readable as-is, without having to parse it.
I'm really fed up with those "alternatives to alternatives to alternatives" that will just get abandoned or unsupported or better yet is just a more clusterfucked solution to a better existing and simple ones
@@stephan4932 it's either the title of this video is misleading or people that get this as "alternative" is misleading just extend the markdown or stop treating this as an alternative whatsoever, as someone stated in the comments: "ADoc tables are not recognizable as such if you don't already know the syntax" - the syntax of this "solution?" looks like a mix of lua, toml and rust And the thing that boggers me is that we've gone on another layer of abstraction that will separate yet so something simple from a future defined standard Does this tool look good? Yes Does this function good? Looks like it Does this require everyone to rewrite\switch existing docs? Yes Does this have backwards compatibility? No Hence solution to this "solution" is - either it needs a backwards compatibility and not yet another "tool" that will convert .md to .adoc or it needs to be a sort of plugin to existing solution i.e. markdown
0:58 1. For source code use code blocks and files should not be in documentation anyways 2. you can export markdown to pretty much anything 3. no big deal nowadays, but holy fuck. AsciiDoc tables look ugly! 4. The Mermaid extension for Markdown exists for exactly that reason.
There is an alternative to markdown and ascii doc that has all the features one could want and it is basically supported by all browsers and even most document programs like word. It's called html. It's been around for a very long time. I wonder why people have forgotten about it?
Mb better, but I'm not adopting it. I have 40ish FOSS libs documented in md. And a tool i built to add functions to markdown, which allows the embedded files and lots of other features. It's a build step, so at the end you still just have regular markdown.
how good is pdf generation incase of multiple pages ? i have used html to pdf before its not good for multiple pages, i will give this a try for multipage dynamic pdf invoices.
The pedant in me really doesn’t like the name. Sure, we might understand ASCII as (plain-text) but it really isn’t. It was a standard for and by Americans for English speakers. The standard was eventually “expanded” to include more characters, but that was still very Euro-centric.
It is not a better alternative, at all lol. I mean maybe if you use markdown on its own, but who does that? You would obviously use something like MDX and SVX and add in Rehype or Remark plugins. Add on top of that front matter, and yeah, sorry but AsciiDoc sucks in comparison. The tooling around markdown alone makes its multiple factors better in every single way.
I usually find it difficult to render Markdown to multiple formats (HTML, epub, pdf, etc). Especially in combination with extensions; if I'm writing a book, I need some basic features like captions and control of the size of images. That being said, I still went with MarkDown due to the popularity and maturity of the ecosystem.
In defense of Markdown tables: Markdown - and by extension, its tables - was originally designed to be human-readable in plain-text form (and I think it still does that pretty well, regardless of flavor). ADoc tables are not recognizable as such if you don't already know the syntax.
And that's exactly why I like and will continue to use markdown
@@pwall But will you continue to use markdown??
@@ResursatorI think he's saying he doesn't like markdown
I'm pretty sure this happens when you copy and paste in Markdown...
Yes. Their syntax is not human-friendly. On a bright side, you can use CSV to format tables in asciiDoc.
All syntax problems are either personal preference or solvable with simple (and common) extensions. Markdown flavours, while different, are all similar enough it causes no problems unless you are using advanced features.
All the rendering stuff at the end (syntax hiloghting, PDF format, etc) is the job of the renderer, not the format. The only reason it’s “consistent” with ASCIIDoc is because there is only one tool to handle it.
Apart from that there are 3?
Can't be a markdown replacement if it's not human readable in plain text
It is though?
@@lostsauce0When people talk about markdown being human readable in plain text, they don’t just mean that it is literally English language text. The point is that Markdown syntax should have the same visual implication even when it hasn’t been parsed. eg., a Markdown table in plain text looks like a table, with rows and columns. An Asciidoc table is just a list until it’s rendered.
@@quantumstormgames2741 You can for simple table, as having each element in a new row is not mandatory
[cols="1, 1"]
|===
| this | is a valid
| 2 columns | table
|===
When you need a complex table with vertical or horizontal span or sub-table, all of which is possible in asciidoc, than you're out of luck
@@quantumstormgames2741but markdown has no tables, some implementations do, but that's not a standard.
@@w01dnick The original markdown spec has no tables, but that’s hardly still what defines what markdown is lol. GFM includes tables and that’s one of the most popular MD standards today. Besides, that was just one vivid example of what I meant. The difference between markdown’s readability and something Asciidoc is visible in basically every type of formatting element
This seems like a classic case of the “15 competing standards” problem lol
Sure, markdown is two years later than asciidoc, MD is redundant.
And I'm not sure what part of this video doesn't make it clear that markdown is not a standard, so calling it one is simply hilarious.
@@rvowles99 I’m not calling it one, I’m calling it 14 different ones lol
@@w01dnick The point of the “15 competing standards” problem isn’t to say that whatever product was developed later is worse lmao its just saying that if people haven’t agreed on one solution, you probably won’t be able to convince them to. I didn’t know that AsciiDoc was created before MarkDown, but all that suggests is that if Markdown managed to become the predominant tool today, it’s probably better lol
@@quantumstormgames2741these two specs are not even competing. They serve different purposes. Markdown is obviously used more because it's more convenient for software developers to document their software in a simple and efficient manner (especially considering reading raw files via terminal via ssh).
However Markdown is not meant to be used for bigg advanced research papers, books, improvised Jupyter Notebook replacements (look at Markdown Preview Enhanced, it's very powerful, but not always reliable nor consistent) etc etc.
And this is exactly the role that AsciiDoc excels in. It's robust, consistent, doesn't have a million ways to do the same thing, opinionated, doesn't require you to install gigabytes of binaries (unlike say LaTeX) and still pretty readable in plaintext (again unlike LaTeX), and it's also usable on the web (unlike LaTeX).
Lost me at plugins, LaTeX, etc. Like jfc why does everything need to be a framework or abstraction layer now. Why can't people just write a standard that actually solves the problem instead of outsourcing it?
Bro yapping
Yeah I'm not sure this is an alternative to markdown at all. It seems more like a document design tool & specification than merely a markup specification.
@@arnerademackerI see it compete with orgmode in that regard.
I think this is actually a good point. We should favour simpler solutions with fewer abstractions. I think plug-ins are okay here because generalised solutions tend to be more complex then specialised ones (since they must handle all cases). So I like having a generalised base for common tasks, but plug-ins that specialise where necessary
@@tom-delalande Agree. Plugins make sense for niche problems like embedding a videogame as it's not something that can be solved in a general manner and won't even work for most output formats. However something basic like diagrams or scientific notation is obviously something you want to be possible without worrying about if it's supported by your specific compiler or output format.
Syntax doesn't even need to be nice, just give me a way to draw arbitrary shapes and glyphs relative to one another and provide a function syntax so third party libraries can use the standardized shapes API to implement whatever they want
I wrote my bachelor thesis in Pandoc Markdown, converted to latex, made changes at 5AM and then sent my thesis-final-final-final to the prof as PDF per e-mail. What a time to be alive.
Looking back, I should've used typst locally using community VS Code plugins and such (I cannot upload my thesis on the typst site, as it contains NDA restricted information).
Btw, the "sane" use of Markdown to create PDFs, sites and such, would be to use Pandoc and write filters for it, which can parse specific tokens to represent tables and other fancy stuff. (i.e. embedded files, the code snippets you mentioned, latex expressions, mermaid js integration (which is possible in some markdown editors!), etc.).
The difference between AsciiDoc and markdown would be that the former has more "built-in", but technically... using pandoc... you get also these features "built-in" using filters (or easier: markdown editors like Typora).
(P.S.: Jetbrains Fleet got recently Markdown Preview and they are working on AsciiDoc support for Writerside)
I've never had such a nice concise video that demonstrated the pros so practically, great job!
Can it export to markdown?
which markdown? 😀
@@Kingside88any flavor.
Damn, I just checked pandoc's site, and even that can only export TO AsciiDoc, not FROM it.
I presume you could use pandoc to do that.
point 2 is already solved for markdown by pandoc. consistent markdown export to any format, supports inline latex if you want it, and output format is fully customizable. can even have one source markdown file export to pdf, html, and PowerPoint slides.
Exactly this. The video feels like some PHP newbie complains about PHP 5 while in reality PHP 8.3 is available and has basically improved anything.
I just look to using markdown because my goal isn't to make a pretty document. It is merely because the formatting generally leaves a well understood document that you can follow along without being worried if it is being rendered or not by some fancy graphic renderer. The rendering is a bonus not required.
I just feel this goes one step I've over. I mean everyone has different needs so I am not saying it is bad of course. I use the bare bones of MD mainly because I just want to separate sections and have documentation that gives me some clear intent or meaning without becoming superfluous and cumbersome.
I know what is a list and can find and understand it without renderer. I know what headings are and what level usually denoting what layer I am in and so forth.
All I need is consistent Latex, so I'm sold
Probably just uses KaTeX under the hood, so why not go straight to the source ;). Seems like yet another standard, which doesn't accomodate everybody again anyways, so let's just hand-roll a renderer for whatever the situation requires, if it's special enough so that markdown won't suffice anymore.
Granted -- They've done a very thorough job documenting the standard, and covering a lot of potential use cases.
But I feel like "complete" is an unreachable goal, because one person really needs LaTex rendering, and the next will ask "why doesn't it natively embed GeoJSON as a map?" (etc, etc).
Markup languages can not really be feature-complete (HTML isn't either), so they will also never be fully consistent (HTML isn't either). Some website full of GIS geeks will offer support for GeoJSON, and before you know it you'll have different adoc flavors.
Org-mode is the best one, tbh. But you need to use Emacs.
Yeah, I wish Org-mode got more exposure.
I agree, everything mentioned here is easily possible in org mode and it has good support in places like github already.
It feels that we are comparing apple to oranges here.
Typically, when using markdown, I use HTML tags. I like this alternative; thank you for sharing.
This looks awesome! I love markdown but the small inconsistencies does complicate things sometimes (and tables are painful 😅). I don't want more features, just more consistency.
I'm gonna give this a try. Great video!
The look of exporting of a markdown being customizable is a feature not a bug. The raw plain text form of a markdown being readable is a design goal of markdown.
I mean, if I want this much control, I would just use an automatic tool to generate docs from source codes. The main point of a Markdown is that there is no special syntax, so you write it as if it was a plain text file, and is meant to be accessible even for non-programmers. The formatting is just cherry on top.
When you start adding codes into Markdown just start to miss the points
You just described adoc. :)
I guess I'll have a look, thanks for sharing
great, can you please make a detailed tutorial/explanation on how to use it?
No offense, but learn to read docs, before writing your own.
@@_modiX I already did that, I just need some tips and workflow suggestions, also I'd rather be guided by someone who's already using it than to blindly do it myself. besides, it's more fun to watch a video than to read lol.
@@_modiXHe just asked for a tutorial.
@@_modiXoffended.
YESSS ASCIIDOC IS THE GOAT
People don't seem to be getting that markdown's issue is it's complete and utter lack of content heirarchy or... organization in general beyond just headers. Or metadata. For more "longform" content asciidoc is wonderful, the point is that you can quickly (and reliably, which is huge) then convert it to PDF, e-reader formats, HTML etc. from that one source file.
With the exception of the table column per row syntax, Markdown can do all those things too. Source code highlighting, LaTeX formulas, diagrams, etc. all work in Markdown too. For more complex tables one needs to fall back to HTML code, which I think is the biggest problem with using Markdown.
You can do most of this already in iA Writer. There I do tables in my CSV editor (MarkupTable) and just hit save. It auto-updates the contents and I still have a nice UI to work with. I link and include sections by just reference the file names. A lot of markdown tools support this.
Seems nice, personally markdown together with padoc does everything i need. An features like diagrams are also available in the places I need them. Though nice to know of an alternative. Thank you for that concise overview ^^
Thanks Tom! Pretty interesting!
cool never gonna change from markdown but interesting none the less
Sweet video! I’d consider slowing the pace down a bit; I found myself rewinding and pausing a lot to comprehend what these features actually meant.
MD is used everywhere, making it the format/tool of choice, end of video.
"Stick to established standards if you want people to contribute."
No content heirarchy, no metadata, etc, markdown is a steaming pile of garbage for longform content
Incredible video! Definitely will look into it!
can't wait for TypeDown
Very Informative, Thanks!
yep, agree that markdown is nice but inconsistent. will check this out.
Looks like fire! I gonna try it
Thanks for bringing this, this looks cool
To be fair: most of the advantages you give can be solved by Pandoc Markdown and Latex
Can you sell me on why I should choose this over my beloved org mode?
The only reason not to use org mode is portability or you don’t use emacs. It is probably one of the most robust formats around. Neorg is getting quite good too. But I don’t use emacs anymore so markdown is good enough and very widely supported. Org mode is actually the only thing I miss about emacs.
Don‘t think AsciiDoc is an alternative, cause they got different philosophies.
Markdowns: „The idea is that a Markdown-formatted document should be publishable as-is“
AsciiDoc: „Publish presentation-rich content from a concise and comprehensive authoring format“
I enjoy markdown a lot. When it comes to programming snippets I like the highlighting of different languages and usually make notes via comments in that particular language. But with tables I do have issues. I would love to scale them or to position them in two areas of view. In latex this is done pretty straight forward. With Latex there is tikz to draw nicely so if a markdown language supports this latex addon it's fine. Is there a way to build presentation in viewable landscape pdf form out of the box? There is a cool python program that takes a pdf an puts it into a presentation mode with highlighting and a dashboard to see all pages and suchs. It's called impressive but does not seem to be maintained any more.
Actually sold me I'll look into it
thanks for this will try it out
I'll agree that Markdown tables suck. I don't use them. What I did with Parsedown and my personal wiki. was to use the ```fenced```` code blocks and the ```language...``` bit at the start. So if I want to include char delimited data, I use ````csv sep=|...```` using Parsedown to format each of the cell contents (i.e. bold, italic, link, etc), and then prevent Parsedown from further processing it.
Org-mode ftw
This sounds like org mode with extra steps
More like a limited subset of Org. In a different accent. 😉 I find asciidoc to be a fine piece of kit, but I have a handful of fundamental disagreements. Nevertheless, adoc is still much, much better than markdown, which can frankly just f off and never return.
So you're telling me human today can't read without beautiful rendering? That's sad.
I thought Pandoc was the key tool to render ascii doc. Does it have its own cmd utilities?
Have you tried Typst?
You mean I need to render it to read it ?
I find it unreasonable as a replacement. I still open a lot of md file in vim or plain text cuz it's convenient. I don't want to go open another source file just to see what function was quoted. The video's great but asciidoc just is not imho.
Yes, those are two different things. AsciiDoc is for writing source files to be rendered somewhere while Markdown is just plain text that can be rendered if needed. One of the design principles of Markdown is, that it shall be readable as-is, without having to parse it.
Asciidoc - 2002.
MarkDown - 2004.
And I see there no signs of the more instruments with it support or improvement of the already existing one.
I'm really fed up with those "alternatives to alternatives to alternatives" that will just get abandoned or unsupported or better yet is just a more clusterfucked solution to a better existing and simple ones
What is your solution?
@@stephan4932 it's either the title of this video is misleading or people that get this as "alternative" is misleading
just extend the markdown or stop treating this as an alternative whatsoever, as someone stated in the comments:
"ADoc tables are not recognizable as such if you don't already know the syntax" - the syntax of this "solution?" looks like a mix of lua, toml and rust
And the thing that boggers me is that we've gone on another layer of abstraction that will separate yet so something simple from a future defined standard
Does this tool look good? Yes
Does this function good? Looks like it
Does this require everyone to rewrite\switch existing docs? Yes
Does this have backwards compatibility? No
Hence solution to this "solution" is - either it needs a backwards compatibility and not yet another "tool" that will convert .md to .adoc or it needs to be a sort of plugin to existing solution i.e. markdown
@@k3ywarriorBackwards compatible for what, itself or another standard we don't know about?
0:58
1. For source code use code blocks and files should not be in documentation anyways
2. you can export markdown to pretty much anything
3. no big deal nowadays, but holy fuck. AsciiDoc tables look ugly!
4. The Mermaid extension for Markdown exists for exactly that reason.
Welll you've convinced me.
except theres no language server---
Looks good
Where is AsciiDoc to HTML Java viewer?
this seems better i no every way
what shell prompt are you using?? 😮
I’m using Starship with Fish
@@tom-delalande care sharing your configuration?
Buuut... does asciidoc support unicode?😅
yeah but can it use unicode?
I haven't watched the video but Html tags are best.
i'll givve this a try
Yeah, 2.5 minutes are way too long to watch...
Looks cool. MD is enough for me tho
Obsidian ftw.
What ide and terminal do you use? 😮
The shell is fish, prompt is starship. Terminal could be any of the greats: wezterm, alacritty, kitty etc.
There is an alternative to markdown and ascii doc that has all the features one could want and it is basically supported by all browsers and even most document programs like word. It's called html. It's been around for a very long time. I wonder why people have forgotten about it?
HTML is very verbose. You'd also use AsciiDoc for rendering to other formats; such as epub and PDF.
Absolute gem that Prime reacted to you.
The problem with Asciidoc is that it's not popular so most tools won't support it. Even an AI struggles with this format.
@@bananatoofat are you ok?
Adaptation takes time.
@@jabuci or can failed. I just warm ppl. I have used Asciidoc for a few years and I don't see better support.
@@jabuciAsciidoc - 2002, MarkDown - 2004.
@@avastorneretal Oh, I thought asciidoc was the new guy. Then markdown won.
Mb better, but I'm not adopting it. I have 40ish FOSS libs documented in md.
And a tool i built to add functions to markdown, which allows the embedded files and lots of other features. It's a build step, so at the end you still just have regular markdown.
how good is pdf generation incase of multiple pages ? i have used html to pdf before its not good for multiple pages, i will give this a try for multipage dynamic pdf invoices.
You add explicit page breaks to make exporting easier for multi page documents. The syntax is `< <
The pedant in me really doesn’t like the name. Sure, we might understand ASCII as (plain-text) but it really isn’t. It was a standard for and by Americans for English speakers. The standard was eventually “expanded” to include more characters, but that was still very Euro-centric.
Markdown is good but AsciiDoc is better ❤
Just learned Quarto/Pandoc. Maybe I'll look at this later.
Check out R Markdown too, for the sake of completeness.
Thanks, but I'm not moving away from markdown 😊
seems more like markup than markdown
Very good video. However I think you need to step back from the microphone and slow down your speech slightly.
you sold me on asciicode
It's not a better alternative. AsciiDoc is orders of magnitude more complex than MD. That's the point of Markdown anyway.
It is not a better alternative, at all lol. I mean maybe if you use markdown on its own, but who does that? You would obviously use something like MDX and SVX and add in Rehype or Remark plugins. Add on top of that front matter, and yeah, sorry but AsciiDoc sucks in comparison. The tooling around markdown alone makes its multiple factors better in every single way.
Content heirarchy.
I usually find it difficult to render Markdown to multiple formats (HTML, epub, pdf, etc). Especially in combination with extensions; if I'm writing a book, I need some basic features like captions and control of the size of images.
That being said, I still went with MarkDown due to the popularity and maturity of the ecosystem.
Makdown
Steps. Steps. Why are we adding more steps. Everything single thing you mentioned I don't care about.
Markdown is fine. Not bothering with this.
Html table are much better imo
But the name is worst yo xd
No, it's not a better alternative, shut up
This just sounds like a slightly worse version of typst - but maybe i'm biased because I need my math symbols 🥲