As I said in my comment, the BTree rewrite was a breaking change. It required all users to dump and reload their DBs. (1)
You do agree that things like that are best done ASAP, right?
I want to see feature completeness too but with more people adopting the project every day, and beginning to use it in semi-serious situations, pushing file format changes through quickly is just good release practise.
(1) if it's the one I'm thinking of. The other you could be referring to just needed a view rebuild; still annoying but nothing like the file format change
5x speedup by integrating with erlang direct, and the HTTP is still there if you need it. So there goes much of the premise of the blog post. Needless to say, the DB itself has still not been optimised for speed - not even close - so this is far from the last word on the project's ultimate speed potential.
This is why you don't read too much into the current performance characteristics of alpha software.
"Personally I would much rather see feature completeness first"