Quoted post unavailable.
Unfortunately I don’t think markdown is going anywhere. I think I see it far more than ever and there’s no sign of it slowing down.
131–140 of 373 posts
Quoted post unavailable.
Unfortunately I don’t think markdown is going anywhere. I think I see it far more than ever and there’s no sign of it slowing down.
Quoted post unavailable.
I’m slightly relieved reading this. I see markdown everywhere, I can’t stand it, and I wonder why people are so crazy about it. It’s nice to know I’m not alone. Unfortunately I don’t think markdown is going anywhere. I think I see it far more than ever and there’s no sign of it slowing down.
Quoted post unavailable.
Is Markdown perfect? No. I find it rather frustrating that there isn't a single definitive flavor, but it's easy to learn, easy to read and render, and can be used as a tool in just about anything. You can keep your 'real programs'.
Quoted post unavailable.
Quoted post unavailable.
Earlier quoted context omitted.
I just run the wiki in docker and take regular snapshots? I also find the requirement "have internet" is a good trade-off against the requirement "install client on every device".
How is docker easier for most people? How does docker even work with multiple devices? Mobiles? and how much storage does a docker-snapshot wastes?
This link gives me a 404. https://help.obsidian.md/Plugins/List+of+plugins
Last I checked there was no good way to do quick capture of articles from mobile iOS to obsidian. Scenario — I come across an article on my iPhone, and I just want to dump title + URL (maybe even the text content) into obsidian. This is a must have for any note taking tool. Anyone have a good workflow for this, please share. Ideally an iOS shortcut.
Quoted post unavailable.
* They work easily with Gi
* They are understandable without a specialized program
I'm curious to what you'd suggest as an alternative to text (yaml, json, ini) configuration files.
Quoted post unavailable.
I think the reason for programmers' attachment to Markdown isn't just about being able to operate on it in a terminal. It's about the general interoperability of plaintext.
Terminal editing is one example, but even IDEs and non-terminal text editors also use plaintext. There's also the fact that version control tools are designed for line-based plaintext. Markdown is especially often used for documentation that gets checked in alongside code, so this is an important consideration.
I would be very interested to hear thoughts on good alternatives to Markdown for technical documentation, even if not plaintext-based.