Clean up documentation for v0.1.0 release

CHANGELOG.md

@@ -2,7 +2,7 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 
-## [Unreleased][unreleased]
+## [0.1.0] - 2016-12-16
 ### Added
 - Basic data structures
     - Range

docs/acknowledgements.rst

@@ -7,7 +7,9 @@ For all of these reasons I use the GenomeTools library extensively in my researc
 
 However, it's no secret that development in C is no walk in the park.
 I've spent more hours troubleshooting memory management and chasing memory leaks than I ever care to again.
-The performance of bare-metal ANSI C is nigh unmatchable, but as a research scientist *my ability to implement and evaluate prototypes quickly* saves me much more time in the long run than a constant-factor speedup in my research code's performance.
+Of course, the performance of bare-metal ANSI C is nigh unmatchable, but as a research scientist *my ability to implement and evaluate prototypes quickly* saves me much more time in the long run than a constant-factor speedup in my research code's performance.
+On the other hand, consider maintenance burden: the initial release of **tag** weighs in at < 1000 lines of code (excluding ≈ 1000 lines of testing code), which could easily require 10000s or 100000s of lines of code to implement in C.
+Finally, implementing **tag** in Python makes for a seamless integration with an ever growing ecosystem of robust data science tools.
 
 So I'd like to acknowledge the GenomeTools community for blazing the trail and (especially Gordon Gremme and Sascha Steinbiss) for their tireless support.
 I'd also like to thank the Python community for their support of a wide variety of tools that made implementing, testing, documenting, and distributing the **tag** package a pleasure.