To be honest, given the exchange on the pull request and the content of the ADR I came to this formulation (https://github.com/linagora/james-project/pull/3309#issuecomment-620957935) 'that I am not hostile to it', but would also like a broader feedback (thanks for asking for it!).
To give my own opinion: I personally agree for Scala local usage, in implementations, or some reasonably isolated APIs (eg: Event Sourcing), as long as Scala usage is not required for James overall understanding. If it helps making the code more readable and maintainable, reduce the complexity of some specific pieces of codes, then it likely is benefic. I think the pull request you refer falls in this category. I am more concerned when we start using Scala in some core API (like mailbox-api), as it forces all developer to understand another language and can makes future contributions harder by increasing the entry barrier. (As detailed here: https://github.com/linagora/james-project/pull/3336) Best regards, Benoit On 08/06/2020 15:58, Matthieu Baechler wrote: > Hi, > > Sorry for the previous mail that I sent by error. > > We specified that we wanted to be polyglot-friendly in James and also > that for the current people writing code we would start using Scala in > some specific context. > > It's what is written in adr 24 here : > https://github.com/apache/james-project/blob/master/src/adr/0024-polyglot-strategy.md > > I personnally like Scala very much and refactored IMAP search which is > a very verbose piece of code today in Java to a more readable Scala > version: https://github.com/linagora/james-project/pull/3309 > > Benoit expressed some doubts about whether that important component > should be written in scala or not here > https://github.com/linagora/james-project/pull/3309#issuecomment-616367598 > > I don't know what to think about that: do people will be afraid of > reading and/or writing Scala? Will it be a way to make people more > interested because Java feels something from the past? > > I don't really care if this code get merged or not but it's a good > occasion to gather people opinions about that and move forward with > James as a project. > > So, what do you think ? > > Cheers, > > -- Matthieu Baechler > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org > For additional commands, e-mail: server-dev-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
