We normalize the results for all four data sources above. Then we add the results for a framework across all data sources. The result is the index.
Why is JSF there, isn’t it a presentation layer framework (and not even an implementation), not a “web framework”?
— While indeed JSF is not the web, but a presentation level framework, a lot of people respond to the question: what web framework are you using with JSF. That’s how it came to be in the index. A similar argument works for Vaadin, and others not so rigorously web framework entries.
Isn’t Spring boot the same as Spring MVC and JHipster?
— From the point of view of what’s on the inside, yes. It all boils down to being a chain of technologies: servlets, Spring MVC, Spring Boot, JHipster. Where every layer adds something: autoconfiguration, project generation, etc. However, if you ask someone what framework do they use for their web app, some people say Spring MVC, some Spring Boot, some JHipster. We know, we asked. That’s why these are separate entries. If you really think that is so incorrect, add these three values together.
Where is my favorite framework?
— We’re always ready to add more frameworks to the index, we started with a small set just to see if there’s any interesting data to share. There is! So if you know a framework you’d like to see in the index, please reach out to us: firstname.lastname@example.org
Are we still in the 15th century? Why is Struts there?
— Perhaps, due to the ranking formula, any technology popular at some point of time has the luggage and is still quite high on the list. It’s hard to obtain correct information about the frameworks used for new projects, so the index is heavily influenced by the past. The main idea behind the index to illustrate the trends in popularity, not the absolute numbers.