Reviews by real users

Just finished a project using open source libraries and have fresh impressions?

Write a review to share your experiences with open source!

On DevRates we focus on reviews by developers using libraries on their daily work.

Technology radar

Launching a start-up or commercial project using open-source libraries? No time to evaluate various technology stacks?

Interested in the latest trends and top-rated open source projects for all layers of your application?

DevRates contains projects reviews of most popular tagged categories and programming languages.

Build your skill profile

Join DevRates and build your public profile from libraries you know and experience positions from projects you've been involved in.

Follow projects and don't miss any news from blogs and twitter on your wall.

Your company is looking for talented developers? Register on DevRates and show your technology stack on your company profile.



No description

User experience

Used technologies not defined

All used projects

User reviews


Gradle provides all the benefits of Maven (build conventions, plugin ecosystem, dependency management, and nested builds) without the need for rigid adherence to arbitrary conventions. A greenfield Gradle project can benefit by sticking with defaults that are sensible and a brownfield project can create configuration customizations that will allow you to port virtually any build structure to Gradle with minimal effort.

Gradle's only weak points are where the build system is so flexible that at times it is hard to track where your changes mess with established documentation (in these cases you've sort of made your own bed so it's your own fault for getting so far off track). Most of the major IDE's support Gradle so the tooling is already there. Over all, Ithere is no other build system I would choose to start a new project with and there are very few legacy projects that wouldn't benefit from getting upgraded to a gradle build.

read full review

read full review
Scroll to top