I would qualify this by saying yes, put the source code in the book, but only if there is something to learn from reading the code. That used to always be the c

I would qualify this by saying yes, put the source code in the book, but only if there is something to learn from reading the code. That used to always be the case, but now there's so much boilerplate required for libraries and frameworks that it's obviously a waste of space to put it there. But if reading and understanding the code is part of the learning process, then yes, it should be inline as part of the experience of reading the book.