 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
8 messages in org.codehaus.groovy.userRE: [groovy-user] HQ gets more game b...| From | Sent On | Attachments |
|---|---|---|
| Jon Travis | Mar 25, 2008 9:39 am | |
| Keith Thomas | Mar 25, 2008 9:44 am | |
| Guillaume Laforge | Mar 25, 2008 9:49 am | |
| Jon Travis | Mar 25, 2008 10:33 am | |
| jbi joe | Mar 6, 2009 4:12 am | |
| Guillaume Laforge | Mar 6, 2009 5:38 am | |
| Peter Bell | Mar 6, 2009 6:50 am | |
| Jason Smith | Mar 6, 2009 7:19 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | RE: [groovy-user] HQ gets more game by being Groovy! | Actions... |
|---|---|---|
| From: | Jason Smith (jsm...@infotrustgroup.com) | |
| Date: | Mar 6, 2009 7:19:52 am | |
| List: | org.codehaus.groovy.user | |
Sounds like someone is grumpy today. :-( Awwww.
Seriously, though...
1. Debugging isn't difficult. The compiler just doesn't catch all the errors at
compile time. You find them pretty quickly when you run the code. Compiling
isn't debugging last I checked. If you are a messy typist, you have to debug
through a lot more cycles with Groovy because the IDE doesn't tell you when you
misspell something all the time.
2. If you don't like the API, use the Java API. It's okay. I think .each and
.findAll are pretty intuitive, personally, but to each his own.
3. Undocumented features? Really? I had not read anything about that. Can
someone reference a wiki page or something?
4. Asked and answered. See #1.
6. The exceptions you get are sometimes unclear, until you get used to the
exceptions. Then you usually know pretty quickly what's going on. When you
started programming Java, all the exceptions it threw were clear? No, you just
got used to them and now they feel natural.
7. Okay, now you've gone too far. Hold me back! Hold me back! Why I oughta...
-----Original Message----- From: jbi joe [mailto:jo...@daggerpoint.net] Sent: Friday, March 06, 2009 5:13 AM To: us...@groovy.codehaus.org Subject: Re: [groovy-user] HQ gets more game by being Groovy!
I have been using groovy for about 9 months with FuseHQ doing a variety of tasks. I really like it alot for the simple tasks. However, IT HAS NOT been of great help in doing many of the tasks. Its like using a script language to program, except very obtuse. Here are my REASONS for NOT using it for most tasks. 1. DEBUGing is very difficult. It allows you to make MISTAKES in your code. 2. The API is very difficult and not java like. 3. There are a lot of "undocumented" features. Dont paint yourself into a corner! It lets U. 4. Most errors are only caught at run time where java would have hit them during compilation. 5. With FuseHQ, its unclear what is happening "under the covers", there is NO java API, that I found. 6. Most of the errors that you get using groovy are not very clear, like some of the exception is hidden. 7. To perform a combination of groovy/java is unwieldy cause it allows java bugs too!
--------------------------------------------------------------------- To unsubscribe from this list, please visit: