Valid point and one I've thought a lot about, especially before pitching Scala. IMO, most non-trivial codebases require learning new grammar. I spent a few yea

Valid point and one I've thought a lot about, especially before pitching Scala. IMO, most non-trivial codebases require learning new grammar. I spent a few years working in Capital Markets and those guys were hacking together their own DSLs in Java for foreign exchange trades, etc. Looked nothing like Java. Libraries like that are almost guaranteed to be written/rewritten in Scala as more banks adopt it. Grammar is as much a business domain concept than a programming language concept, so cool that Scala supports different lingos so well. Hopefully in the future we won't see as many poor workarounds for language inflexibility, Ie, all the horrible duck programming done by IBM with WebSphere Commerce. Grammar aside Walmart is a different beast than most apps. Handling huge spikes in traffic (Ie, Black Friday) was more a factor than new hires learning new grammar. We also had to handle massive amounts of data for catalog processing with Akka which wound up nearly being a DSL in itself. Pairing and a solid dev process is so important. That said if I worked on a different app with different reqs, less spikes in traffic, more developer turnover, etc, I may have used something else. Lots of factors to consider. Grammar is definitely something to watch with open source Scala projects though. We'll see if a more canonical lingo develops over time.