Guillaume Laforge's DSL talk shows this rather nicely. Language is Groovy, context is writing DSLs but you will get the idea.
Slides 12-17: http://www.slideshare.net/glaforge/practical-groovy-domainspecific-languages-springone-europe-2009 Cheers, Paul. On Wed, May 6, 2009 at 11:10 AM, Dave Watson <[email protected]>wrote: > > What does this mean, exactly? Can you elaborate more about the 85% of > your code that is boilerplate? > > Not trying to argue, I'm just very puzzled by what this might mean.... > > On May 5, 5:27 pm, Viktor Klang <[email protected]> wrote: > > Greetings posse, > > > > having spent more than half a decade writing API:s in Java I feel that > since > > Java 5 was introduced, more and more time has to be spent writing > > boilerplate API code to try to save the API consumers from jumping > through > > hoops in order to get stuff done. Because we all want easily consumable > > libraries, don't we? > > > > Having jumped onto the Scala bandwagon about 1½ years ago I feel like the > > ratio of business end code of Java is appro 15% while in Scala it's more > > like 65% > > > > <observation>You can most likely substitute "Scala" in the text below > with > > any non-Java JVM language</observation> > > > > With Scala getting more and more cleaner to be consumed by Java code, > isn't > > there plenty of good reasons to switch to Scala for library code, while > > letting the application developers stay i Java-land? > > > > -- > > Viktor Klang > > Known from the Internet > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
