I've written 4 technical books including the Classic Computer Science Problems Series (https://classicproblems.com). I agree with what Thorsten said at the end—none of this really matters—or it's marginal at most. Most people who say they want to write a book lack the motivation to do it. It's not the tools getting in the way.

Apress used Word templates back in 2013 when I did my first book with them. Manning let you use asciidoc or Word templates when I worked with them. I wrote my first book with them in markdown and translated to asciidoc using pandoc. There were so many formatting issues and I found the tools for asciidoc so immature that I ultimately went to using their Word templates on my next two books with them despite preferring purely text formats.

Now I'm working on my next book and I think I'm going to try self publishing. I'm liking leanpub's use of a markdown like format. But again none of this really matters. You can fix formatting later. You have to sit down and write!

PS Thorsten's "Writing an Interpreter in Go" is great: https://amzn.to/3yLTJjE

> Writing an Interpreter in Go https://amzn.to/2PA5LEh

+1

I cannot recommend Thorsten Ball's books highly enough. They're really fantastic, step-by-step tutorials, and you certainly don't need a CS degree to understand what he's doing.

Writing An Interpreter In Go https://amzn.to/2FYwwiQ

Writing A Compiler In Go https://amzn.to/2sLilph

Writing an interpreter in Go https://www.amazon.com/Writing-Interpreter-Go-Thorsten-Ball/... is pretty good. The book assumes that you know Go and the resulting interpreter is not a Lisp.

Writing an Interpreter in Go is a very elegant book for learning how to write an interpreter from scratch using Go. Worth every cent: https://www.amazon.com/dp/300055808X

[2] https://interpreterbook.com/