The first answer is that Pharo/Smalltalk is unique in that a running system/IDE contains all source code, all documentation (class, method, help, tutorial), all unit tests and all runnable examples in a very easy, accessible way. It takes some getting used to, but this is actually better and much more powerful than any alternative. It would be a mistake to view Pharo programming in the same way you view other languages.
The second answer is that there are lots of books and articles that take the classic/structured book/paper approach. There are http://books.pharo.org, http://themoosebook.org, http://book.seaside.st/book, http://medium.com/concerning-pharo and many more.
The problem I find with today’s developers is that they are rather closed-minded. They are rigid and inflexible, and not willing to adapt to new and different ways of doing things. In my generation (circa 1980–1990), people didn’t have a problem with trying different technologies. That’s why I had no issue with learning Smalltalk 10 years ago, after I had retired from a 20-year-long career in C systems programming and FORTRAN scientific programming.