Read this with the "don't learn frameworks; learn the architecture" article :-)
Off topic: why not use npm instead of grunt, gulp, etc. Two nice articles on that: NPM for Everything and How to Use NPM as a Build Tool
Not a particularly fluid presenter. If your presentation has a lot of "I won't explain this now ..."'s, then maybe reconsider giving it. A presentation should be self-contained unless it's clearly part of a series of lessons.
This talk still looks at JS as the source of interactive user experience ie. helping science 'reach out' to users. But from here how long before JS as a language of scientific/engineering computation.