That would imply writing n(n-1)/2 "X for Y devs" articles, or an O(n^2) complexity.
A much better way would be to have an universal standard, possibly abstract framework with which all frameworks are contrasted. This way, only n comparison articles need be written, giving a linear cost.
Sorry, could not abstain. OTOH, this principle is mighty useful when writing conversion software. Just write converters to and from a standard format.
Having done web development exclusively in Python (Zope,...,Django), I some time feel that I may be missing out on the advances in a large ecosystem like J2EE(Spring etc.,)
I don't think you're missing out on a lot, and that's coming from someone who uses both Spring and Django daily. There are a lot of Spring projects, but just to give you an example:
- Spring Security --> django.contrib.auth
- Spring MVC --> well, Django urls, models, views and templates.
- Spring Core/Beans (the dependency injection part) --> do you think you need it?
In the average JEE project, that's all you'll be using as far as Spring goes. Or maybe add Spring Integration or Spring Batch.