Does this replace Book module?

Does this module replace the book module? Probably not for everyone, maybe for some. I haven't been following Book 2.x development, and don't intend this module to be a rewrite of the book module.

This module came about because we need some of the Book module's functionality, but wanted a better UX and a more concise archtecture.

This module will not replace book module feature for feature, and we're not planning on writing an upgrade path from Book to this module.
This module provides a lightweight alternative to the Book module with different architecture and a smaller UX footprint (books in this module are just managed only on the main book node, and all the pages are just normal content.)

It's was based around the Entity Reference Hierachy module because I liked the architecture, the UX/UI experience work well for book editing, and it works with the Migrate Default Content module.

To clairify if someone did write a migration from book to this module, we would accept it.

Great thank you. I'll explore Entity Reference Hierarchy some more and compare differences.