> Part of the saturation levels of tooling has to do with the job market. .. but it works like this: You have this thing that you can use for all kinds of pur

> Part of the saturation levels of tooling has to do with the job market. .. but it works like this: You have this thing that you can use for all kinds of purposes, called ECMA Script, or JS. As marketing people say, it "adds value to the product" Problem with it (the JS) is that it is really easy to get started with it. So, the people that have spent years developing these fancy (value add) "solutions" rightfully fear for their job security, as: - when the time comes that they should demand a raise, the manager might rightfully reason that the added cost isn't worth it as they could just train a college grad for the job much cheaper. So, what do they (experienced devs in big corps) do? They build "Barriers To Entry" so called: Teh Frrrrrameworkz! ta-daa Invent convoluted layers upon layers on top of this very simple yet efficient thing, JS -- layers that grow so complicated that they require significantly more study and practice to master than the very simple tool (JS) that anyone can learn to solve very basic tasks with in an hour. That way they make "development" a bureaucratic standardized hell of a process in stead of just "getting things done", and the effect is that they increase their own job security. ...and you can still accomplish the same things in vanilla JS, only these "developers" (now as senior as to being the ones doing the employment interviews) spend great effort trying to convince every new/potential colleague that you can't. End result: all teh Interwebs filled with "spinners" and lazyload and much other user-hostile stuff built to satisfy automated testing, search engines and whatnot - not users. Very little that "just works" ... and a totally recalibrated job market, introducing roles/functions such as DevOps and much other nonsese like it.