[jecxjo]

I actually wrote my own in Haskell, but really I just mean the structure. I no longer need huge ordered lists of blocking dependencies. I loved that taskwarrior did that, but once your life becomes less complicated, all the cool features seemed to get in my way. I wanted burndown charts. I wanted an app to figure out what tasks were highest priority based on how much time they could take and deadlines. But once you no longer have any of that...it is basically todo.txt

Edit:

I should also add that with my daily life (outside of work) I'm strictly a pencil and paper kinda guy. I hate when my phone dies and I have no idea what I'm supposed to do today.

Might as well return the shameless plug with my own (https://github.com/jecxjo/todo.hs)

[jacobevelyn]

Thanks for all the info! Glad to hear I'm not the only pencil-user on HN :)

[stewbrew]

There are some extensions that bring task dependencies to todo.txt. IMHO outlines are a quite natural extension of the original format that can be used for that without making things too complicated.

[jecxjo]

I totally agree. I am currently trying to figure out how to best do that with todo.txt with the minimal amount of dependencies. I liked in taskwarrior how all the tasks were numbered and could be referenced, but it required a big infrastructure in taskwarrior, which is more painful in todo.txt.

[stewbrew]

There is no use in numbering tasks in todo.txt files. But you (as a developer) can create an id based on the current time stamp and the tasks content that can be referenced later on. The VIM ttodo_vim plugin does it this way.