Please log in to watch this conference skillscast.
Groovy started life as the dynamic symbiote to Java. In order to achieve this Groovy wasn't totally "duck typing", it supported optional runtime type checking. It was though still very much a dynamic language with a full meta-object protocol, competing with JRuby, Jython and Clojure for market share.
With the additional of @TypeChecked and @CompileStatic and other things, Groovy has entered the realms of being a statically compiled language, competing with Java, Scala, and Kotlin for market share.
Is this the right direction for Groovy to go? Is claiming to be both a static and a dynamic language ruining the Groovy message? Is it ruining Groovy? Is @TypeChecked fundamentally different from @CompileStatic? This session will investigate these questions and may serve as a place to learn about these things or a place to debate the future direction of Groovy.
YOU MAY ALSO LIKE:
- Microservices from the very start with Russel Winder! (SkillsCast recorded in June 2017)
- How to teach IntelliJ IDEA to your juniors (Online Meetup on 2nd February 2023)
- Saving Costs with Pragmatic Serverless Java Architectures (SkillsCast recorded in November 2022)
- Preparing Apache Kafka for Scala 3 (SkillsCast recorded in October 2022)
Is Groovy Static or Dynamic?
Russel is an ex-theoretical physicist, ex-UNIX system programmer, ex-academic, ex-independent consultant, ex-analyst, ex-author, ex-expert witness and ex-trainer. Russel is still interested in programming and programming languages, and all things parallel and concurrent. And build.
He's actively involved with GPars, Me TV, and various bits and pieces of SDR. Russel likes working with Python, Ceylon, Kotlin, D, Go, Rust, and C++17.