+1 for consistency. On Fri, Jul 24, 2015 at 8:51 AM, Neha Narkhede <n...@confluent.io> wrote:
> Personally, I prefer the consistency and 2 spaces for indentation. Although > I'm in agreement with Jay about the ambition to eventually move the server > code to Java, I'd hate to make that a blocker for discussing a simple > change like standardizing on java/scala indentation :-) > > On Fri, Jul 24, 2015 at 8:07 AM, Ismael Juma <ism...@juma.me.uk> wrote: > > > On Fri, Jul 24, 2015 at 2:00 AM, Jay Kreps <j...@confluent.io> wrote: > > > > > I do agree that working with a mixture of scala and java is a pain in > the > > > butt. What about considering the more extreme idea of just moving the > > > remaining server-side scala into java? I like Scala, but the tooling > and > > > compatibility story for java is better, and Java 8 addressed some of > the > > > gaps. For a system like Kafka I do kind of think that what Scala offers > > is > > > less useful, and the kind of boring Java tooling like IDE support, > > > findbugs, checkstyle, simple exception stack traces, and a good > > > compatability story is more important. > > > > > > I can certainly see the case for avoiding the complexity of two different > > languages (assuming that the benefits are not worth it). However, I am > not > > sure about the "findbugs, checkstyle" point. Static checking is an area > > that Scala does quite well (better than Java in many ways): scalastyle, > > abide, scalariform, wartremover, scapegoat, etc. And Scala 2.11 also has > a > > number of Xlint warnings. > > > > Best, > > Ismael > > > > > > -- > Thanks, > Neha >
