In Paul Simon’s song, The 59th Street Bridge Song(Feelin’ Groovy), he tell us to "Slow down you move too fast, You got to make the moment last, Just kickin’ down the cobble stones, Lookin’ for fun and feelin’ groovy". Well, I for one don’t want to slow down that often, especially when I am programming. I am always looking for fun, especially when I get to interact with great development teams. I am blessed with a wonderful family, work for a great company, and love what I do for a living, so I always feel groovy!
Where is this blog entry going, besides down memory and musical lanes? I’m headed towards Groovy, the agile, dynamic (some would say scripting) language that exists on top of the Java Virtual Machine (JVM). Groovy was started by Bob McWhirter and James Strachan in August 2003. There have been many other languages implemented on the JVM. Why mention Groovy (besides the great name)?
Being a programming language junkie, I love look at new languages and understand what they bring to our world. From the Groovy home page, the language includes support for (but not limited to)
- Static and Dynamic typing
- Closures
- Collections, Lists, Maps and Arrays
- Polymorphism and Autoboxing
- Native support for markup languages like HTML, XML, and more
- A Path Expression Language
- Support for building Servlets
- SQL support
- JavaBeans creation and use
- Operator Overloading
- Unit Testing
Groovy is part of the Java Community Process (JCP) as JSR-241. Additional information can also be found in the Groovy FAQ.Groovy presentation from OSCon 2004 (Powerpoint format). Groovy presentation at JavaOne 2004 (PDF format). Additional insights into the Groovy language can be found in Mark Volkman’s article, "Groovy, Scripting for Java".
{ 3 } Comments
Can Borland reinstate the Delphi for Java project which was suspended a few years back now that Delphi supports class helpers? ;o)
Forget all of this - code in machine or assembly language. All the rest is just for wusses.
> code in machine or assembly language
I agree - it is almost the ultimate, "close to the metal" way to program. The only closer way would be to reprogram the chip itself.
I spent the first 9 years of my programming career, after college, as an assembly language programmer building real time mini-computer systems at TRW. It was a great way to start after all the progrmming language and compiler classes in college.
Nowadays, I can look at high level language code and visualize what is going on in the generated/optimized code. Makes debugging much easier to know before you look in the CPU Viewer.
Post a Comment