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

Used projects

web framework
web server
message broker

User reviews


Trying to be honest in my review (since I'm the creator of the project).  Tapestry is simple, but I'd like to make it simpler.  Documentation is good, but there are not any up-to date books currently available.  I may be under-estimating the community, though.

full review »
Sign in to vote for review score: 2

I've switched over all my builds from Ant and Maven to Gradle, and never regretted it.  Most common things you want to do are built right into Gradle. 

I have found that the documentation, while verbose, can be a bit of a maze, with a mix of user documentation, JavaDoc, and the "DSL guide", all linked together. The big issue is that what you can put in your build depends on what properties are exposed by what objects, and often that's determined by the implementation class provided by Gradle, not the interface class defined in the DSL. So you can run in circles until you stumble on your solution.

Like many projects, the docs focus on what you can do vs. common usages.  Using Gradle effectively is an exercise in learning how to read and understand those docs.

That being said, Gradle is the best tool for builds, and the one that's easiest to extend. I've had bad experiences with other tools, but Gradle has yet to let me down.

full review »
Sign in to vote for review score: 1

I love Spock quite a bit ... I've actually converted hundreds of TestNG tests over to Spock.  Documentation is sparse, and a work in progress, but the framework does so much with so little, that this is not an impediment.  You will go very quickly from seeing it to the first time to feeling quite fluent, and that's nice.

full review »
Sign in to vote for review score: 1

I'm a big fan of CoffeeScript; I prefer to write all my JavaScript as CoffeeScript.  As they say, "using CoffeeScript will make you a better JavaScript programmer".

Debugging with CoffeeScript can occassionally be a challenge, that's true.  The benefits more than make up for it: concise and readable makes  a big difference to me.

full review »
Sign in to vote for review score: 0
Scroll to top