I appreciate how much work stuff like this is, thanks.
There's something weird to me about how the data is broken out though. The article claims Django and Rails dominate - "the gap between them and the next thing is really big". This leaves the impression that those are the big backend stacks.
Yet there's no mention of node. Go? Java stacks? Clojure backends? I know that node and go and Clojure aren't frameworks (and meteor is mentioned)... but that's the point, I think. The bins are chosen in a way that they seem to exclude a huge chunk (maybe the majority!) of tech stacks.
I agree with the case of Go, the std lib does good enough job to be full-toolbox. Go is getting really big. If want you can check the numbers from the first part [1] where I mention that. You can find number other languages as well there. But still, if you think about I wouldn't be too fair to compare Go with Ruby on Rails.
Nice series of posts... Though, I don't like the graphics for the language popularity in the first one. The inconsistent scales make ruby look similar in popularity to php and perl where it's an order of magnitude more popular than perl and almost that much higher than php. The other thing is that you didn't label the vertical axis.
But the point still stands that Go's stdlib is practically a web framework. Especially considering the level at which the community away from frameworks and towards simple idiomatic use of stdlib.
Also, hiring trends for newer technologies doesn't necessarily indicate anything aside from a labor shortage. The chances that a company can hire a sharp Spring Boot developer without advertising are much higher than the chances that you know a great react developer with years of experience.
There's something weird to me about how the data is broken out though. The article claims Django and Rails dominate - "the gap between them and the next thing is really big". This leaves the impression that those are the big backend stacks.
Yet there's no mention of node. Go? Java stacks? Clojure backends? I know that node and go and Clojure aren't frameworks (and meteor is mentioned)... but that's the point, I think. The bins are chosen in a way that they seem to exclude a huge chunk (maybe the majority!) of tech stacks.