The graphs are drawn as line charts, with everything being points on the line. This creates the illusion that every technology goes through a lifecycle between all of these states in the exact same path. This is utter nonsense.
Take for instance, your technology graph, where you list "Augmented Reality" as being in the "Disillusionment" phase. Being a point on the curve, along with every other point on the curve, it's implicit that someday "Augmented Reality" may move to be more widely adopted in the "Productivity plateau." But that may never happen; it may just end up being a fad that Nintendo tried to make money off of and never really succeeded at. Nevermind that it's debatable what "productivity" is for a concept like AR.
These graphs also give no real useful information on their Y-axis. It's not really useful to know if the author thinks that Swift is about to peak and that Java has plataued. It may be extremely useful to know how many people are starting new Swift projects, relative to other langauges in the same niche (e.g. Obj-C, maybe Java if you want to include Android? Idk it's not my niche). That might be information someone can use to decide whether they should start a project in Swift or do something else.
Also, the selection of these charts themselves is a little odd. Why a chart devoted just to PHP frameworks? Is this the State of Dev or the state of people who only know one language and read about the rest in school?