[throwanem]

I think that goes to both your point and mine; sure, the website does a little more in that it can be accessed from computers other than the one where it's running, but he also needed a whole book to do not much more than scratch the surface of what we call "web programming".

That's not to say it isn't a significant accomplishment, and he should be proud of it!

[parasubvert]

I don’t know that it is only scratching the surface - the book gets you into an interactive site that is styled with Bootstrap, uses a database, uses web APIs, pushes to Heroku so it’s HA and scalable, etc.

It’s pretty much all the major elements of web programming but using the more elegant ways of simplifying the experience.

I’m not denying the complexity just saying that there are still many (particularly in Python or in cloud PaaSes) who value streamlining the experience.

[throwanem]

I'd still call it scratching the surface in that I doubt it goes into details on how any of those things actually work, and that's an important consideration because it's the basis for knowing how to deal with any of them going wrong. No doubt you'd have been able to provide support in that case, but it still goes to the point of there being a much larger potential depth of complexity here.

I get the sense the book tries to surf the reader over the top of most of that ocean, and that's reasonable enough, but the ocean is still there. I wouldn't consider it all that comparable to Hypercard, which in this metaphor I guess is more like the town pool back when those still existed? People who are ready for the deep end can dive into it, and people who feel like paddling around in the shallow end is more their speed can safely do that too.