I watched web frameworks like Rails, Grails, etc. I'm used to making applications in the Spring Framework with Hibernate ... and I need something more productive.
One of the things that I realized is that while some of the things in Grails are sexy, there are serious problems with this. Grails Controllers:
1) implemented horribly. Apparently, they cannot propagate to superclasses at runtime. I tried this to add basic actions and helper methods, and this seems to cause the grains to explode.
2) based on an outdated model of request parameters (and not on support objects, which are much nicer).
3) hard to check. Command objects are handled in a completely different way ... and in fact, it is MUCH more difficult to write a test than to write controller code.
4) Command objects act in a completely different way. They are pre-checked and linked, which causes a lot of inconsistencies than the basic parameter model.
5) Command objects cannot be reused, and the pain in the back is to reuse most of the material from domain classes, such as constraints and fields. This is TRIVIAL to do mostly Spring. Why the hell wasn’t it trivial to do in the Grail?
6) The forests that are generated are pure shit. It does not generalize inserts and updates ... and actually copies / pastes a bunch of code in two forms: create.gsp and edit.gsp. The views themselves are giant piles of dog affairs. This is further compounded by the fact that it uses low-level parameters, not objects.
Integration tests are 30 times slower than the Spring integration test. It's disgusting.
Some mocking tests are so difficult to write and are not guaranteed to work when you deploy it, I believe that it speeds up the fast tdd test cycles.
Most things seem to wrap grails while it is running, like adding taglib or something really. The server reboot problem has not been resolved at all.
Spring/Hibernate/Java - . , , .
, , Scala... , Hibernate.
. -, . Grails - , Controller.
, ?