Due to my long time away from such matters, the proposed YAML engine for Java that I intended to create have not got so far. Right it seems as if YAML is a major bottleneck in JRuby, so I started looking around. Loo and behold, at http://jyaml.sourceforge.net/ there seems to exists something that's almost exactly what we need. So I've impromptu decided to discontinue my JAML project and instead tackle the task of making this engine work together with JRuby.
RubyGems is really close right now. Each step takes us closer and closer, and right now it feels as if we have 99.99% of everything needed. If just the SourceForge CVS-system could start working we could actually really get this of the ground now.
tisdag, april 11, 2006
fredag, april 07, 2006
JavaOne is go
Alright, San Francisco: here we come! Our development group is going to JavaOne together this year. Actually, this is the first time there has been a development group to talk about, since I was it's only member until this summer. And there seems to be much fun going on. I'm particularly looking forward to the sessions with a focus on other languages. Sometimes I find it strange to have lots of Java Certifications and still loathe the language.
Things I'm not going to miss: The JRuby session, Best practices with Generics and other Tiger features, What's new and exciting with AspectJ, Rapid web application development with Grails, Portlet Best Practices, Trails in depth, Server-side scripting, Scripting in Mustang, Effective Java reloaded, Mustang and Dolphin. And these are just a few. Wow, it's going to be a busy week, and trying to meet up with lots of friends and contacts in SF is going to make a complete experience of this.
By the way, it's interesting to see that there are many sessions on Spring, Dependency Injection and other stuff that make Java lightweight. One title especially caught my eye: "DI: Configuration Files Must Die". My take on the configuration file-issue is to have it as executable as possible. A project I'm working with on and off in purview of Ologix will use Common Lisp and judicious use of macros to create the configuration information. The nifty thing about this is that I haven't yet decided what the main language will be. It could be Lisp, it could be Ruby or it could be Java. But whatever I choose it will still be fairly easy for me to handle the configuration issue. In Lisp I can just read-eval it, in Ruby it's very easy to parse and in Java I could use Jatha and expand the macros to calls into the Java structure. Not very efficient, maybe, but configuration is not performance. Flexibility is king.
Hope to see you in San Francisco.
Things I'm not going to miss: The JRuby session, Best practices with Generics and other Tiger features, What's new and exciting with AspectJ, Rapid web application development with Grails, Portlet Best Practices, Trails in depth, Server-side scripting, Scripting in Mustang, Effective Java reloaded, Mustang and Dolphin. And these are just a few. Wow, it's going to be a busy week, and trying to meet up with lots of friends and contacts in SF is going to make a complete experience of this.
By the way, it's interesting to see that there are many sessions on Spring, Dependency Injection and other stuff that make Java lightweight. One title especially caught my eye: "DI: Configuration Files Must Die". My take on the configuration file-issue is to have it as executable as possible. A project I'm working with on and off in purview of Ologix will use Common Lisp and judicious use of macros to create the configuration information. The nifty thing about this is that I haven't yet decided what the main language will be. It could be Lisp, it could be Ruby or it could be Java. But whatever I choose it will still be fairly easy for me to handle the configuration issue. In Lisp I can just read-eval it, in Ruby it's very easy to parse and in Java I could use Jatha and expand the macros to calls into the Java structure. Not very efficient, maybe, but configuration is not performance. Flexibility is king.
Hope to see you in San Francisco.
Current status
Due to massive loads of work I have been unable to write here for a few months. That will probably change as of right now, since the current projects are finally soon closing down and the workload returns to more or less normal.
Oh, and if you for some reason haven't read Steve Yegge's stuff yet, go do it here and on his blogspot here. This guy know what he's talking about.
Oh, and if you for some reason haven't read Steve Yegge's stuff yet, go do it here and on his blogspot here. This guy know what he's talking about.
Prenumerera på:
Inlägg (Atom)
