[shaki-dora]

Let's see, going by the index, which technologies are younger than a year (the logic being "would your statement have made sense a year ago" because I obviously can't prove if a technology will still be relevant a year from now):

Internet/web: no

Web browsers: no

DNS: no

HTTP: no

Web Hosting: no

UI Design: no

HTML: no

CSS: no

SEO: no

JavaScript: no

DOM, BOM, JQuery: no

Web Fonts: no

Accessibility: no

... and so on. But maybe you meant just Javascript libraries, which seem to make up just a small part of the content, but ok... Let's use "Module/Package Loading Tools" as a sample, because this thing is really to big to go through everything:

Browserify: Started in 2012. So... nope

Rollup: Started in 2015. No (but close!)

SystemJS: 2013. Nope, sorry

Webpack: 2013. Nope

And let's arbitrarily add the behemoth:

React: 2013. Nope

It appears there was an awful lot of new frameworks in 2013 and that let to the impression of framework churn. To perpetuate that narrative four years later seems to be more groupthink than reality.

[ravenstine]

What people are feeling as "framework churn" is probably more like framework uncertainty.

[milesrout]

Those 2013 frameworks didn't get to the level of completion necessary to become popular until 2015, really.

[sapeien]

jQuery has had the reputation of being very antiquated for a while. The problem that it set out to solve no longer exists. The same will be true of what you mentioned above.

Now there are tools that solve problems that arise from other tools, it is getting very meta. An ecosystem like this cannot last indefinitely.