A lot. For personal projects, I'm going with RoR (though I'll be giving a shot at Phoenix in the near future). Sometimes I also miss static type checking and many other things Java enforces, but I feel compensated when I don't have to compile/recompile when I change something small. JUnit is faster, but RSpec looks better (just have a look at it). About template engines, HTML/ERB is the default but you can use HAML, or even better, Slim. I don't think there's something similar to replace Thymeleaf with. About ORM, I have mixed feelings, Active Record feels too magic, but this magic enables you to easily integrate your models with the database and not worry much about it. Finally, securing Rails applications is pretty straightforward. Rails doesn't bring in by default something like Spring Security for authentication but the Devise gem is good enough in this regard. IMO, Bundler and Ruby Gems is better than Maven/Maven Central. Also, IMO, when comparing major dynamic and interpreted languages, Ruby has the best OO model, Python feels lacking in this regard.
In general, IMO, RoR is about going fast while producing a good product in the end, and having enjoyable experience in the process. RoR is great for prototyping, but its good enough for a final product too. Java/Spring is rock-solid and time tested, feels better suited for really big projects with really big teams, as Java strictness and verbosity begins to help instead of eating productivity.
For my average web development needs, RoR is better, at least for now.