Email or username:

Password:

Forgot your password?
5 posts total
Felix

Here we go, my new outliner wiki (for certain values of "wiki") outliners, note-taking apps and everything codeberg.org/nosycat/outliner-

[DATA EXPUNGED]
Felix

@bouncepaw Thanks for reminding me of TreeSheets! Gave it another chance, and this time it's a keeper. Now I want to start a wiki or something about outliners and note-taking apps.

Felix

I've been asked why not simply use in AntiWiki, and it turns out there are many good reasons:

- Markdown is an extra dependency.
- It's noticeably slow to parse and render.
- It's overhyped and overused. People are fed up.
- There must be better ways to do lightweight markup.
- Only nerds ever liked Markdown to be honest.

Besides, turns out my new markup language is really nice to use. Might as well.

I've been asked why not simply use in AntiWiki, and it turns out there are many good reasons:

- Markdown is an extra dependency.
- It's noticeably slow to parse and render.
- It's overhyped and overused. People are fed up.
- There must be better ways to do lightweight markup.
- Only nerds ever liked Markdown to be honest.

6DoF Motion

@felix, I agree that plugging md or html into every editor product is overkill. Coming from a </markup> background, markdown was a guilty pleasure and using anything but the core spec felt like using the wrong tool for the job. For me the ideal usage is to make pure text more readable in simple unformatted text editors and it does that very well. The uplift to editor markup is a side benefit of having a spec, but once lifted I rarely go back to the md, since I've exceeded its requirements.

Felix

I'm back on my usual bullshit with yet another tool to help people make websites, except a somewhat novel formula for a change: felix.plesoianu.ro/web/antiwik

Go Up