<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial, Helvetica, sans-serif; font-size: 10pt; color: #000000'>While not just stay with Java? I don't understand the need to mix another language into codebase, which has little support compared to java. If it's just to make your efforts a little faster, I would argue you loose value in the project by having yet another aspect to the learning curve for every other developer.<br><br>Betamax was better than VHS and laser disc was before it's time. Sometimes it pays to follow the masses, when you expect them to use your product ;)<br><br><br>----- Original Message -----<br>From: "Michael Neale" <michael.neale@gmail.com><br>To: "Rules Dev List" <rules-dev@lists.jboss.org><br>Sent: Monday, January 12, 2009 6:41:42 PM GMT -06:00 US/Canada Central<br>Subject: Re: [rules-dev] Scala<br><br>Yeah netbeans is getting pretty decent scala support - improving all the time.<br><br>people are using the eclipse one, so it is slowly getting better, its<br>just that it is unstable that troubles me.<br><br>yes, as Mark said, groovy is fine, but its quite a different language<br>in semantics if not syntax. Whereas scala is probably more a 1 for 1<br>replacement (although it can have a stepper learning curve in some<br>areas) and a very fast powerful language (not that for this bit speed<br>is too sensitive).<br><br>Whilst initially there may not be automated refactorings, as it is a<br>static language (you tend to never require reflection in it) it can<br>cope with manual refactorings much better then java (as you get<br>compile errors and warnings for any missed changes).<br><br>Initially I am looking at it for a testing module that uses<br>spreadsheets, so will see how that goes (its fairly isolated).<br><br><br><br>On Mon, Jan 12, 2009 at 1:02 PM, Edson Tirelli <tirelli@post.com> wrote:<br>><br>> I like the functional aspect of scala and the way it promotes some<br>> modeling good practices. The main worry is really, once we start<br>> implementing things on it, to maintain that codebase, and for that tooling<br>> is paramount. So, if maven works well and IntelliJ can do some minimum work<br>> on refactories, I like the idea of an incremental inclusion of scala<br>> components where they make sense.<br>><br>> []s<br>> Edson<br>><br>> 2009/1/11 Michael Neale <michael.neale@gmail.com><br>>><br>>> Hey All. I have been looking into scala for sometime, and recently<br>>> started using it for a testing tool (kind of a replacement for the<br>>> "fit for rules" library).<br>>> I have been quite impressed with it, the tool integration (with<br>>> intelliJ) is outstanding, and it works nice with maven (even with<br>>> mixed java source).<br>>><br>>> Assuming this goes well, I am thinking of extending the usage of scala<br>>> to the server side components of bits of guvnor (obviously the client<br>>> is still GWT). Probably in a small way at first (I have found that<br>>> common annoying bits of code in java can be much clearer in scala -<br>>> examples to come !).<br>>><br>>> I was interested in what people think about this? Does it make it<br>>> harder for people to get into the code (I am not aiming to write the<br>>> densest scala, just use it when approriate)?<br>>><br>>> The main downsides I see are: Eclipse support - the plugin for eclipse<br>>> for scala is not great at the moment (netbeans or intelliJ would be<br>>> better), and general familiarity for people to read (although I<br>>> personally think it would take anyone who reads this list minutes to<br>>> learn enough to follow the simple things I would do).<br>>><br>>> Thoughts? Objections?<br>>><br>>> FAQ: Why scala? well its closer to java in intent then all other<br>>> popular JVM languages (ie its static) and compiles down similarly to<br>>> result in similar performance (better in some cases). I use "closures"<br>>> a lot (thanks to GWT that got be in the habit) but the inner class way<br>>> of doing it in java gets combersome.<br>>><br>>> --<br>>> Michael D Neale<br>>> home: www.michaelneale.net<br>>> blog: michaelneale.blogspot.com<br>>> _______________________________________________<br>>> rules-dev mailing list<br>>> rules-dev@lists.jboss.org<br>>> https://lists.jboss.org/mailman/listinfo/rules-dev<br>><br>><br>><br>> --<br>> Edson Tirelli<br>> JBoss Drools Core Development<br>> JBoss, a division of Red Hat @ www.jboss.com<br>><br>> _______________________________________________<br>> rules-dev mailing list<br>> rules-dev@lists.jboss.org<br>> https://lists.jboss.org/mailman/listinfo/rules-dev<br>><br>><br><br><br><br>-- <br>Michael D Neale<br>home: www.michaelneale.net<br>blog: michaelneale.blogspot.com<br>_______________________________________________<br>rules-dev mailing list<br>rules-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/rules-dev<br></div></body></html>