Slashdot Mirror

... which pays better?

at npm charts: https://npmcharts.com/compare/react,angular,@angular/core,ember-cli,vue

Frameworks can be useful, but it seems like the framework treadmill is in full swing.

Here's another view at the data, Brutal Lifecycle of Javascript Frameworks

The measurement is done based on new questions and that measuring usage by "activity" is kind of ridiculous. New frameworks seem much more likely to generate SO questions. Questions about an older framework can be answered by looking at an existing project, from a blog post, tutorial or from (shock) already-written SO answers. While the data aren't conclusive either way, I think it's more plausible to believe that much of the sharp decline is due to saturation of answers to many obvious questions.

There's also the question of how to measure 'usage' of a framework or language: is it number of new projects, number of new lines of code or amount of traffic served?

Finally, it seems like actually the number of SO questions might have some negative component correlated to usage. Wouldn't we imagine (?) that the frameworks/languages that are intuitive and that have excellent documentation would both be preferred by developers (I sure do) and would lead to fewer SO questions. Again, this is speculation, but it goes to the question of what in the world the SO trends are actually measuring.

TLDR: Their measurement methodology is (poorly defined and) bad and they should feel bad.

Ruby is ahead of Perl, in the "medium-disliked" category. I find it amusing that Ruby was conceived as a Python replacement, yet fell hopelessly behind in the popularity contest.

If you look at the original article -- cobol is there, as the 3rd most hated "tag".

The original study is here I found the "polarization of technology" diagram at the bottom even more interesting.

The trend can be seen much better from the original article, in the programming technologies visited by income chart.

More details on why
https://stackoverflow.blog/201...