171–180 of 373 posts
Quoted post unavailable.
> To represent lots of different information to humans in a concise view, you need a lot more than Markdown is capable of. [•••] > Better tools for composing documents already exist. Such as? Honest question, and a hope you don't mean MS Word or Google Doc.
It's AGPL'ed.
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.
I’ve never been sent a markdown file that I haven’t been able to read.
I’ve been sent a PDF that looks correct, but I’m not able to easily edit. I’ve never been sent a markdown file that I’ve been unable to edit.
For a document format to be able to be widespread it needs to be interoperable and work on all systems. Markdown is popular because plain text works everywhere.
I’m not convinced that markdown is the ultimate format, but it has more good properties than most other available formats.
Quoted post unavailable.
Quoted post unavailable.
One of my highest priorities for a personal knowledgebase is that my system can continue to be essentially unchanged for the rest of my life (hopefully another 50+ years), just as my current archive of notes goes back 20 years. The Lindy Effect[0] would say that plain text files have already existed for more than 50 years, therefore are likely to still exist another 50 years from now. That being said the Obsidian tea…
If Roam goes bust, so does my data. If Obsidian goes bust, I'll just have a bunch of markdown files I can import elsewhere.
Not to mention Obsidian seems to try to add as few weird syntax as possible
Quoted post unavailable.
>In fact, the whole programmer's fetish with writing everything with a plain terminal text editor needs to die. Markdown, YAML, JSON, INI files. It's the year 2021 for christ's sake, and we're composing documents with tools designed for green CRTs! Alternative take for this same sentiment: It's the year 2021, why has nobody figured out better ways to present knowledge than simple text files?
There are a plethora of alternate ways to represent knowledge. Each has its own set of trade-offs. Which do you prioritize?
Ease of editing Interoperability/readability in multiple systems Expressive styling Optimized for configurations Optimized for readable text Etcetera
Fill out that list, stack rank it and tell us which format is better.
> With Obsidian, your data sits in a local folder. Never leave your life's work held hostage in the cloud again. ... says a brochure page for proprietary software.
What is your point? I've moved my obsidian notes to vscode and back without any issues. Is closed source software somehow incapable of having true statements?
"It's funny to be criticizing user freedom and lock-in issues with other programs, above a link to buy your stuff from an app store."
> With Obsidian, your data sits in a local folder. Never leave your life's work held hostage in the cloud again. ... says a brochure page for proprietary software.
Did you completely misunderstand the text segment you quoted? It doesn't say that the software itself is open-source/free software, it's just talking about the data it produces/maintains/uses, so your comment seems to be way offside.
Earlier quoted context omitted.
I think the biggest problem with Emacs is that you cannot really make sense of a lot of stuff until you start programming elisp in anger. I tried for many years to copy and paste snippets etc, but now I realised you just need to bite the bullet and learn it like any other programming language and be prepared to do "real development" in Emacs. Its very difficult to be a "tourist" in Emacs, IMHO, a lot of things just d…
Couldn’t agree more. I used to get annoyed that I had to copy and paste code snippets that I found over the Web just to configure basic stuff. It got out of control pretty quickly. Now I understood that Emacs is supposed to be used by programming it. Turns out it was meant to be a feature, not a bug.
I really do need to get started on a personal wiki. I might give this a try. It would be nice if I can get the files into git that I can save to a private github repo (I'm fine paying the one time payment to support them but $8/month seems too much for a simple sync feature)
I setup a cron job to git add ., git commit, and git push everyday at 3am, so that I don’t have to think about it at all. It works great.