How stable is the Groovy language? -


We are writing a large production system in Java, and I am thinking that we can write some components or Not one of the JVM-based dynamic languages ​​is the best choice from the Groovy Java Interoperability approach. But is Jorozo implementation very reliable for use in production (I will agree with this), and is the Groovy language specification stable so that we are not going to modify our production code in a year or two? What are your experiences?

Summary (5/30/09): Good comments, I understand that you should be careful to adopt Groovy for mission-critical production use, this is fine for helpful accessories. By putting together the test cases, and there is a mid-field where this is probably good but performing your homework first is an issue, which should be balanced by the developer's growth in productivity. Bill and Ichoras gave equally useful answers based on Groovy usage, so it was a coin toss

Update (12/3/09): Recently I used to seriously consider another JVM Seeing. It was designed and implemented by Martin Odarski, the original author of the current Java compiler and co-designer of Java Generics. Scala is a strongly typed, but uses the infringing type to snap a lot of boilerplate. This is a good mix of object-oriented and functional programming James Gosling James Strachan, author of Groove,

Update (4/26/11): A styled type of Groove, Is equal to, but take a look I look very interesting.

edit : About four years later, Groovy becomes more concrete Are there.

I can whole heartedly recommend it for production grade projects.


I'm using Groovy to support production applications for a while and for that purpose it is stable enough to be Groovy in realistic output code; I do not think I will do this. Groovy is a wonderful thing in this regard, it has been better in the last year or even longer, but in a short time I will go to a bug that seems to be the generated code (my issues seem to revolve around scoping) The reason is difficult to track down.

I have got away from Groovy (although the stuff we use is simple and solid) is still and I have used dragon (jathan implementation), which in my opinion is too much has been applied. In addition, Python trumps Grivi in ​​readability.

You can turn off some very interesting code in Groovy and operator overloading and whatnot

These languages ​​are used for convenience and speed on auxiliary code ... to whom the goods Can be switched to the flight if needed. None of this is in production. I do not think I would either put it in production unless it was in the form of a major speed or as a stopgap to get something important out of the door in the form of evidence of a concept or prototype.

And in the case of keeping it in actual production, it would be the most frightening of the circumstances and I would have to rewrite some in Java for the next Java release. I'm 98% sure that either production will be fine, but this is 2% too much unnecessary risk.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -