The part I find funny was that the book was about doing network server development with Haskell...on Linux.
Google docs change tracking probably could be taught, but you are dealing with people who spent lots of time in their workflow and who are resisting to adapt for a single author. Mind that those reviewers and editors switch from book to book depending on frequency of author's feedback. The author is just one between many ...
If you look at many contemporary books typesetting is not an important topic for many.
Google Docs have a nice change-tracking and commenting system and next to no learning curve. The downsides are the formatting, which is rather unpredictable for complex-ish documents (figures are always a mess), and citations.
Overleaf helps get formatting and bibliography out of the way, but everybody must know at least some LaTeX, and you have to come up with your own comment-and-response system to keep track of what's going on. There is something baked in, but it is not satisfactory. On the other hand, it is very easy to just comment out stuff that is no longer needed in the main text but may still be useful or just serves as easy-to-see revision history.
I realize it was petty, and there are some regrets in how I handled it, I just thought the anecdote was amusing.
If you're asking because you want help with some network programming you are doing in Haskell then you can PM me on some kind of social media.
Write it as a reference that even you'd find useful, with emphasis on defining the basics and getting them right, and increasingly lighter when it comes to intermediate and advanced concepts. Those can either form future books or consulting or both. Since you've started writing, it's worth it to go through the whole process and publish. I did it with a conventional big publisher some time ago, but I wouldn't do that again today. The idea a big publisher would require you use Word is very familiar to me, and I think it's ridiculous.