remove old section of why rewriting

README.md

@@ -39,31 +39,6 @@ inside the repository. The binary will be named `t` (or `t.exe` if you use
 windows) and it is located inside the `target/release` directory that was
 created during compilation.
 
-## Why did you write this instead of improving timetrap?
-
-* 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). With tiempo you can get (or build) a binary, put it somewhere in
-  your `PATH`, 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. And there are a lot of tests backing this
-  assertions.
-
-### Other advantages
-
-* 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 in the 'text' formatter.
-* Solved some old issues in timetrap.
-* Added new features!
-
 ## How to build
 
 You need [rust](https://rustup.rs), then clone the repo and simply run