> I usually don't downvote answer that ask for 3rd party libraries, just vote to close
why ? why do you do this ? a lot of time there is an exact piece of code that does what OP asks for, what does it change if the piece of code is in a SO answer or in a github project ?
The code is ideally a "this is the code that fixes the problem" and its done. Once there's an answer, you don't often get a dozen more answers with slightly different code.
Library recommendations however - everyone has their favorite. Someone recommends Spring. Someone else recommends Play. Someone else recommends Stripes (and then has a dozen comments explaining the different between Stripes and Stripe). Someone else has Struts (and then gets a dozen comments about the version they're recommending being out of date and lead to the equifax breech). JSF, Jspx, JHipster, Grails, GWT, ... it goes on and on.
And now that there are a score of answers, some new user sees the post, doesn't read everything and recommends a new version of Spring. Or points to a different site for Struts.
The curation of such a question takes far more work than the question is worth. Look at how much effort the C++ community puts into maintaining the C++ book list. Spending that much effort on each recommendation question is far too much moderation time across the community.
But there are times where I want to see everyone vouch for their frameworks in that exact manor in the stack overflow format by the stack overflow crowd.
why ? why do you do this ? a lot of time there is an exact piece of code that does what OP asks for, what does it change if the piece of code is in a SO answer or in a github project ?