clarify advantages in readme
This commit is contained in:
parent
3fc5ac5111
commit
470df61bba
20
README.md
20
README.md
|
@ -167,24 +167,26 @@ day in the computer's timezone. Add `Z` or an offset to specify the timezone.
|
|||
|
||||
## Why did you write this instead of improving timetrap?
|
||||
|
||||
* timetrap is hard to install, hard to keep updated (because of ruby). Once this
|
||||
tools is finished you can get (or build) a binary, put it somewhere, and it
|
||||
will just work forever in that machine.
|
||||
* timetrap is [hard to install](https://github.com/samg/timetrap/issues/176),
|
||||
hard to keep [updated](https://github.com/samg/timetrap/issues/174) (because
|
||||
of ruby). Once this tools is finished you can get (or build) a binary, put it
|
||||
somewhere, and it will just work forever in that machine. I'm bundling sqlite.
|
||||
* timetrap is slow (no way around it, because of ruby), some commands take up to
|
||||
a second. Tiempo always feels snappy.
|
||||
* needed major refactor to fix the timezone problem (in a language I'm not
|
||||
proficient with). I was aware of this problem and designed tiempo to store
|
||||
timestamps in UTC while at the same time being able to work with a database
|
||||
made by timetrap without messing up.
|
||||
made by timetrap without messing up. And there are a lot of tests backing this
|
||||
assertions.
|
||||
|
||||
### Other advantages
|
||||
|
||||
* Columns are always aligned
|
||||
* Fixed some input inconsistencies
|
||||
* cli interface is much better (ask -h for any command)
|
||||
* man page (to do)
|
||||
* Columns in the output are always aligned.
|
||||
* Fixed some input inconsistencies.
|
||||
* cli interface is easier to discover (ask -h for any sub-command)
|
||||
* end times are printed with +1d to indicate that the activity ended the next
|
||||
day
|
||||
day in the 'text' formatter.
|
||||
* solved some old issues in timetrap.
|
||||
|
||||
## How to build
|
||||
|
||||
|
|
Loading…
Reference in New Issue