3 ms·
> Grails. After two months of work i must say i found it very interesting and productive Two months isn't long enough to gauge productivity - there could be a
by vorg 13y ago
> Grails. After two months of work i must say i found it very interesting and productive
Two months isn't long enough to gauge productivity - there could be a lot of maintenance issues later.
I'm interested to know how many of the Groovy Language features are used in a typical Grails project, or in any Grails project for that matter. I mean, does any Grails project out there, say, transform the abstract syntax tree with Groovy's AST transforms?
- andretti1977 13y agoI think two months are sufficent to understand productivity of a language/platform from the "code development" point of view, at least if you are an experienced developer and have a good knowledge of other languages/frameworks/platforms. I agree that the long-term analisys is always the best and that could be a lot of issue about maintenance and sure, two months aren't sufficent to master specific language features, but you can get a quick overview and feel if it is productive or not. I don't use too much specific features but Groovy offers a lot of interesting things i may adopt in the future. Maybe other experienced developers can answer your question better than me.
- chaostheory 13y agoI disagree. Rails also has huge productivity gains in the beginning. Unfortunately with every major release they keep radically changing how things are done. Leading you to either stagnate with an older version or forcing you to do a semi painful upgrade that gets worse the longer you wait. You're not going to realize this in two months. Fortunately Grails doesn't suffer this problem but my point stands: 2 months isn't enough. 1-2 years is more like it.