i thought it was weird to use express right away for any node article. the obvious concern is that it's easy to conflate ideas when you're learning a library an

i thought it was weird to use express right away for any node article. the obvious concern is that it's easy to conflate ideas when you're learning a library and a platform at the same time. following my expectation, this article is full of quotes that only half make sense to me. "JavaScript and JSON are tightly related, which makes managing JSON in Express about as simple as it gets." "Note that Listing 4 includes a line directing Express to use bodyParser. This will enable us to easily (and I do mean easily) grab attributes from an incoming JSON document." "Listing 5. Adding JSON parsing [followed by a package.json dependency declaration]" managing json in node has nothing to do with express, and bodyParser is not exclusive to json. as for "listing 5", well, i have no idea. perhaps i'm overreacting, but ibm has consistently portrayed a strange understanding of nodejs.