91–100 of 328 posts
Because, like UNIX/Linux itself, worse is better: https://en.wikipedia.org/wiki/Worse_is_better - and perfect is the enemy of "good enough." We want to encourage people to produce written output with minimal friction. Barriers to writing--and especially barriers to producing documentation--should be minimized. Writing well is difficult enough! Markup is overhead. Complex markup is even more overhead. Markdown is the…
Earlier quoted context omitted.
Well, one good reason is that a person who generally doesn't "swear" can then choose to use them very effectively when the situation warrants. If you always go to strongest words when mild ones will do, you're out of things to say when you need to make a stronger/more forceful point.
And there is nothing better to use for the headline than a minced oath if you explicitly don't want to swear? Make it make sense.
Earlier quoted context omitted.
And there is nothing better to use for the headline than a minced oath if you explicitly don't want to swear? Make it make sense.
Perhaps instead of worrying about someone else's free choice to use certain words iver others, it would be wise of you to ask: why would you complain about forced speech patterns in the context of censorship but then be angry when someone uses their free speech differently then you would use it?
Earlier quoted context omitted.
There are other solutions which are as easy to read/write (if not more) and which are defined much better… Asciidoc comes to mind.
"Better specified" doesn't mean better. A bunch of features doesn't mean better. Markdown is popular because it is simple. I have never had to teach anyone Markdown. They look at the file and immediately see what's going on and can copy the style. Occasionally someone may have to look up something like table syntax, but no one in my career or personal life has ever asked me to explain Markdown to them, which is rare…
Bonus: It starts simple but can be used to do whole books if needed.
The article correctly identifies the upsides of Markdown, then identifies a bunch of issues that I, as a casual user of it, don't care about. Then, in the solution section, doesn't identify a solution. No thank you, I'll stick with Markdown.
Because, like UNIX/Linux itself, worse is better: https://en.wikipedia.org/wiki/Worse_is_better - and perfect is the enemy of "good enough." We want to encourage people to produce written output with minimal friction. Barriers to writing--and especially barriers to producing documentation--should be minimized. Writing well is difficult enough! Markup is overhead. Complex markup is even more overhead. Markdown is the…
Worse is better doesn’t mean worst is best either.
Earlier quoted context omitted.
I suggest trying Obsidian for WYSIWYG markdown editing. It beats heck out of typing it raw and eliminates that cognitive load.
I don’t like WYSIWYG editing, as it makes the formatting invisible.
In the worst case, the barrier to entry and exit are pretty low.
Have used asciidoc, HTML, word, latex, and rst.
Markdown is the least painful of all. It's not perfect but the others are worse.
(My custom stack uses markdown (or Jupyter notebooks converted to markdown). Pandoc plus some custom filters creates typst (for PDF) or epub.)