1. EcmaScript vs. JavaScript: The more advanced frameworks like AngularJS(V4), React, and a few others based more on ES5/ES6/ES+ are fundamentally different from those frameworks and libraries that are created using current interpretable javascript, like JQuery and Bootstrap, for example. ES5/ES6 are fully object-oriented, functional programming languages that must be compiled/transpiled to more standard javascript so they can be rendered properly server-side and client-side as necessary.

2. HTML/CSS/JS simplifying (and related compiling/transpiling) technologies: There are a number of HTML templating languages (Jade/Pug, Handlebars, Erb, etc.), CSS templating tools (Like SASS/SCSS and others), standard javascript alternatives (like CoffeeScript and others) that help organize and translate simplified HTML, CSS, and JS functionality into standard HTML5/CSS3/ES4(JS). Each of these need to be understood and their use varies widely across all platforms.

3. HTML/CSS/JS extending (and related compiling/transpiling) technologies: The advanced frameworks like AngularJS(V4) and React need specialized build technologies and tools to compile/transpile them from the ES5/ES6/ES+ standards to more usable HTML5/CSS3/ES4(JS) that can be interpreted by the JS runtime engines like V8, SpiderMonkey, Chakra and others. Current indications are that additional languages (C#, C++) will soon be able to be used as source languages in addition to ES standards, and could be able to be transpiled to run as 'javascript', depending upon advances to the interpreter frameworks and platforms (like NodeJS and other similar platforms under development by major vendors).

4. Build and Scaffolding Tools: The various build and scaffolding tools like Yeoman, Grunt, Gulp, Bower, WebPack, etc. when implementing newer javascript frameworks (e.g. AngularJS(V4), React, etc.) help create a what I consider proto-IDEs - they organize the supporting libraries, integrate specific build/make/transpile tools, and provide a basic structure or prototype application framework. But these newer frameworks are structured around more discrete functional programming design patterns, rather than an application design pattern like MVC/MV+. The correspondence between functional design patterns and application design patterns needs to be more fully explained.

5. REST and Persistence: The REST architecture promotes use of 'fat' clients that are responsible for all local state management. And REST often requires use of all the different persistence options: in-memory data, local data, remote data. And the data can be simple stores of information, key-value pairs, databases (SQL and NoSQL) with all of the access, control and management issues they portend.