sorted by: recent | see : popular

Content Tagged with Groovy + languages

While experimenting with JavaFx Script I encountered a few gotchas switching from Java/Groovy, mostly related to my preconceptions of the language itself. Even though it is JVM language built with Java, being an specialized language for declarative UI building doesn't mean it will follow Java's steps all the way, nor other modern features brought into the JVM by Groovy. The following table summarizes many of the orthogonal features of the three languages, it is not a complete reference for any of them. The "official draft" of the JavaFX™ Script Programming Language Reference was used to learn more about the it. Disclaimer: I know Groovy better than JavaFx Script, if someone spots a mistake please let me know

There has been some discussion going on in the blogosphere about monads, and especially about the Haskell Maybe monad or the Scala option class. Those are ways to prevent problems with NULL and NPEs that Java lacks. A Java Option implementation is more verbose but can be reduced sometimes with using "for" and Iterable.

Both! Groovy is a fabulous language. Just read Groovy In Action and some of the other Groovy books. Just about every page brought a Wow response from this Java developer. And the Grails web stack builds on Groovy to provide a quick and powerful website building experience.

I like the Groovy concept of builders not only for providing a natural implementation of the builder pattern, but you can also look at builders as a way to create handy DSLs. Check out the SwingBuilder, the GraphicsBuilder or the Hibernate Criteria Builder to see how well targeted these DSLs can be.

On Paul's return from JavaOne this year, we spoke about Neal Gafter's Closures Cookbook talk. From what I understood, this was a look at the BGGA closures proposal, and contained an example that pushed hard on some of the tougher closure issues for Java. I thought it might be fun to look at the Java example from the talk, and covert it to Scala and Groovy.

Short answer: as many times as needed until polyglot programming really sinks in. Every day or so a new post on Java's demise appears, this has been happening for quite a while, but the truth is that Java (the language) has a lot of life in the years to come (after all COBOL and C++ are still around), the question is would still be the dominant language in the JVM?

It is simply amazing how many people and how much energy is at JavaOne. All of the movers and shakers of the industry are here to give out sage words of wisdom. Listen to this lighthearted overview of day two and three of JavaOne.

Ah, the saga of misinterpreted micro-benchmarks! Developers advocating one technology over another have long used micro-benchmarks and trivial examples to illustrate their point. This is most often seen in the area of language implementation, where performance is a critical (and often emotional) consideration. The great language shootout is a good example of this.

Guillaume Laforge, Groovy project lead, answers questions from the JavaPosse team, recorded at JavaPolis 2007 in Belgium.

I haven't touched this blog for the past months as life has been very busy since my son was born. But now it's time agains, as I released the Grails Flex Plugin today.

Dynamic Languages Toolkit (DLTK) is a tool for vendors, researchers, and end-users who rely on dynamic languages. DLTK is comprised of a set of extensible frameworks designed to reduce the complexity of building full featured development environments for

Example of using Groovy in TCP listener mode