They're not dying. They've gone through the Hype Cycle [1] and have moved from being new and exciting tools to being just... tools. [1] http://www.gartner.com/

They're not dying. They've gone through the Hype Cycle [1] and have moved from being new and exciting tools to being just... tools. [1] http://www.gartner.com/technology/research/methodologies/hype-cycle.jsp http://www.gartner.com/technology/research/methodologies/hyp... smt88's post is consistent with what I've been seeing as well. Two or three years ago there was an uptick in gradual typing as a transition from dynamic typing to static typing. Functional Programming's influence and inspiration is showing everywhere, from .map() and .filter() utility libraries, to Functions-as-a-Service (Lambda, "serverless") computing, to Java 8, Model-View-Update (where Update is a Pure Function) stuff like Elm, Redux. The NoSQL hype is finally over, we now have datastore decision diagrams that help us pick a database on its merits. We are starting to realize that doing complex stateful logic on the client often means also doing complex stateful logic on the server and synchronizing the two, so single-purpose libraries like React are heading towards a world where we'll be rendering on the server again and just pushing virtual dom diffs on the wire. We have all the pieces right now, but so far no one has come along and done this yet. Opinionated frameworks are falling out of favor; everything is about minimalistic libraries you have to chain together yourself. While this means more creative freedom, it also means more moving parts to orchestrate, and more problems you have to think about yourself.