B) You don't have to literally "choose a path" and only do that, these are different aspects of web development and they are roadmaps for each that lay out a path that the author found useful from start to finish. You can hop between them as you wish, but front-end work is distinct from back-end work and naturally they wouldn't be in the same progression.
Are you purposely being dense? Serious question, because I found this resource to be informative.
EDIT: Adding the disclaimer from the page since apparently everyone wants to interpret this as a be all end all resource due to a bad HN submission title:
The purpose of these roadmaps is to give you an idea about the landscape and to guide you if you are confused about what to learn next and not to encourage you to pick what is hip and trendy. You should grow some understanding of why one tool would better suited for some cases than the other and remember hip and trendy never means best suited for the job