John Carnell

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

I agree with you on Spring. The key thing to keep in mind is that in most organizations they are looking at the question of development frameworks from an either or perspective. They either go light-weight (ROR/Grails) or heavyweight (J2EE). Thats a bit of false dichtomy. There are a lot of problems that can be solved without having to using a J2EE-based solution. However, when organizations only focus on one specific framework they end up incurring a significant amount of cost on projects that they do not need.

The thing I like about Spring (and Groovy) is that it provides a migration path. I can get something out there quickly and if need be fail quickly. As my application needs evolve, I have a way of moving forward without having to completely re-write my code.

Ugly scripting languages :). I can write cruddy Ruby code just as much as cruddy Groovy code. I love Java and have done a lot of work with it. I still write a greal deal of my applications in Java. However, there is a very real need for languages like Groovy. It allows to solve problems quickly. I can pop open the Groovy console and start tinkering with an idea. In Java, I have to an IDE, a workspace an app server, etc.....

Think about what it takes to execute a simple SQL statement in Java. It usually takes 10-15 lines of code. I have to get a database connection, get a preparedstatement, bind my parameters to it, walk through the resultset. I can usually turn it around in 3-5 in Groovy.

I think the key thing to realize is that Groovy is still just a technology. You still need to follow good coding practices in writing your code.

Cheers,

John

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.

Actually, Anthavio I would disagree with you. I understand the client code seems a little obtuse, but the advantage here is more on the server side. Writing an MDB can be a pain especially if I want to implement simple change. Using Spring and Groovy in this case allows me to easily use MDB like functionality in a web-app container or even a standalone JVM.

We have used this with our rapid prototyping teams to quickly string together applications. This is where I see a lot of the power of Groovy. I get a lot of velocity in being able to put together an application. It is also gives me a migration path to a heavier solution if I need to.